# Magist Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Magist

Research which regulations may apply to your product across jurisdictions and industries.

- Record: https://musedirectory.ai/connector/magist
- Category: Legal
- Developer: Magist
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 520ms, checked 2026-10-29T12:46:17Z
- Endpoint: https://magist.io/api/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-28T14:41:09Z)
- Source: Found in the official MCP Registry (io.github.magist-io/magist) https://registry.modelcontextprotocol.io/v0/servers?search=io.github.magist-io%2Fmagist

Magist provides deterministic regulatory research for product launches. Search regulations by keyword and jurisdiction, compute which rules may apply based on your product features and target markets, find compliance controls and vendors, and review enforcement history. Returns research information only; consult a lawyer for legal advice.

Example request: "Tell me which regulations might apply if I launch a social app targeting teens in the EU and US."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Magist to help me. It is a free service with an MCP server at https://magist.io/api/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- lookup_regulation: Look up one regulation by its Magist id and return structured research information: title, citation, jurisdiction, status, review dates, a plain-language summary, and the Controls that may satisfy it. Returns facts about what a regulation says, not a determination of how it appli
- search_regulations: Search Magist’s regulation corpus by keyword with optional filters (jurisdiction, domain, status, content-review status, coverage depth). Returns a paginated list of matching regulations with permanent citation URLs. Deterministic: the same query and filters return the same resul
- compute_requirements: Run Magist’s deterministic compliance engine over a product description (features, target markets, audience age bands, optional business model) and return the regulations and Controls that may be triggered, a complexity tier with a numeric score, a blocker count, and a per-audien
- find_controls: Given a regulation id, return the compliance Controls that may satisfy it, each with a priority signal (blocker / required / evaluate / best-practice) and a short summary of the work involved. Returns research information about typical control mappings, not a determination that a
- find_vendors: Given a Control id, list third-party vendors and in-house approaches that may implement it, with effort/cost signals and a source-disclosure (editorial research vs vendor submission). Magist does not accept payment from vendors and does not rank or endorse them. Returns a neutral
- get_enforcement: Return recent regulatory enforcement actions from Magist’s catalog, optionally filtered by regulation id and a since-date. Each action includes the penalty, authority, a primary-source link, and (where authored) a practitionerAnalysis: a hedged, third-person editorial note on wha
- find_counsel: Search Magist’s open counsel directory for law firms by jurisdiction and practice area. Returns an editorial / firm-claimed directory to help a user identify licensed attorneys to consult. Inclusion is not endorsement; verify bar status and conflicts independently before engaging
- verify_ai_answer: Verify a Magist grounding-proof token: the "groundingProof" field on a regulation or control record from the REST API (GET /api/v1/regulations/{id} or /api/v1/controls/{id}) when the server has signing enabled. MCP tool responses do not carry these tokens. Proves the citation was
- list_feature_catalog: Return Magist’s closed catalogs of valid product feature ids and target market ids, each with a short human-readable label -- the exact identifiers compute_requirements accepts as "features" and "markets". Use this to validate ids before calling compute_requirements; ids outside 

Screening checks:
- MCP handshake: pass (Answered in 371ms)
- Domain against threat feeds (Cloudflare security DNS): pass (magist.io not flagged)
- Published packages against the OSV malicious-package database: pass (No malicious-package advisories)
- Hidden instructions or invisible characters in tool text: pass (9 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)