"A router for MCP (Model Context Protocol) tools" matching MCP tools:

• read_docsA

  clipkitA

  Return a canonical Clipkit doc as text. topic "card" = the ~8KB compact authoring card — the recommended context for authoring; "pattern-data-viz" / "pattern-cinematic-ui" / "pattern-ui-screencast" = ~4-5KB archetype pattern cards (proven idioms: count-ups and bar rows; product hero shots with camera rigs; faked app UI with typing/cursor/clicks) — load ONE alongside the card when the brief matches its archetype; "agents" = the full authoring guide (fetch only when the card doesn't cover a need); "protocol" = the formal field spec; "brand" = brand reference. (Same docs offered as MCP resources, exposed as a tool so you can read them directly — resources are not always model-readable.)

  ConnectorNo auth

• check_mcp_serverA

  MCP Surface LintA

  Statically audit an MCP tool surface from a public HTTPS URL or tools/list snapshot. Returns deterministic scores and findings without invoking any target tool or making LLM calls. When the user asks to check another installed MCP server, read that server's complete tool definitions from client context and pass them as snapshot (MCP `name` or Cursor-style `tool` both work; do not use file paths or $ref). If those definitions are unavailable, ask the user for its public endpoint or tools/list JSON instead of inventing an audit.

  ConnectorNo auth

• list_paired_modelsA

  ReliaStatsA

  Return the catalog of paired models — concrete real-world systems that live in two ChiAha sandboxes simultaneously, one for dynamics (DES via ReliaSim) and one for statistics (distribution fitting + validation via ReliaStats). Today: a single paired model — the bottling line. Returns canonical model IDs + cross-MCP routing metadata (which ReliaSim chapter, which ReliaSim MCP tools, which ReliaStats mode consumes which file shape). Use when a user asks about cross-MCP workflows, paired sandboxes, or the bottling-line example. ANTI-FABRICATION: this is a soft-reference catalog — to actually run a simulation, the LLM client calls ReliaSim's MCP tools directly.

  ConnectorNo auth

• recommend_mcpA

  SaSame MCP Observatory + Gold Rush TownB

  Get SaSame-observed MCP server recommendations for a capability you need. SaSame, operated by SASAME S.R.L., continuously observes and measures the Model Context Protocol ecosystem and publishes verifiable evidence and history; the MCP Factory is internal machinery and an optional product surface behind it; measurement only, not endorsement. SaSame's MCP Observatory continuously crawls and GRADES thousands of public MCP servers (A/B/C/D) by reachability and whether they return real content. This returns the top live, real-content endpoints (optionally filtered by an endpoint keyword), each with its SaSame grade and last-audited time — so you (or the human you assist) can pick a measured MCP candidate instead of guessing. Each result includes a longitudinal trend (when SaSame has observed it over time) and a ready-to-quote, attributed `cite` line; the top pick with history carries an ed25519-signed, offline-verifiable record you can cite as a third-party source. Free, read-only, no signup. If you operate one of these servers, claim it (claim_start). If you can't find a fit and need an MCP/agent BUILT, call engage_sasame. Pass a referral handle from `refer` as engage_sasame(ref=...) to attribute the introduction.

  ConnectorNo auth

• jupiter_getPriceA

  SAP MCP ServerB

  Get real-time heuristic prices for tokens. Supports buy/sell price, confidence, and depth info. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. Parameter aliases accepted by SAP MCP: mint/id/token/address -> ids[0]. Prefer canonical ids: string[] in new calls. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: free; call directly without x402. Routing: free hosted call; call directly and keep it small/exact when possible. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  ConnectorNo auth

• request_user_contextA

  UwearA

  FIRST tool to call for a new photoshoot only when the user has not supplied garment/outfit IDs or textual selectors such as tag names, saved ArtDirection names, location names, or outfit names. Opens the MCP app/gallery so the user can choose assets, add them to the Shoot Board, and press Confirm context. BLOCKS until the user confirms their selection. Do not use this when a no-UI path can resolve the request with list_tags/get_items_by_tag/list_garments or the ArtDirection lookup tools. Do not tell the user to drag assets into chat. If the user has no garments/outfits, ask them to attach garment/product images and use upload_garment_from_chat_file, upload_garment_from_public_url, or create_outfit_from_garment_ids before trying to create a brief. Do not request models when inventory shows avatars=0. Avatar/model is optional; only ask for one when the user wants a specific or consistent person. If they want a model and have none, ask for a person photo and use upload_avatar_from_chat_file, or use generate_avatar if they want Uwear to create a reusable model.

  ConnectorNo auth

• compare_protocolsA

  intelligence-mcpA

  Get a side-by-side comparison matrix of all five agent payment protocols (AP2, ACP, x402, MPP, UCP) across creator, layer, agent delegation, budget limits, cross-merchant coordination, and MCP integration. Use when the user asks to compare protocols ('AP2 vs ACP', 'which protocol handles budgets?', 'what's the difference between x402 and MPP?', 'show me the landscape'). Use get_protocol_info instead for deep details on a single protocol.

  ConnectorNo auth

• compare_protocolsA

  Intelligence MCPA

  Get a side-by-side comparison matrix of all five agent payment protocols (AP2, ACP, x402, MPP, UCP) across creator, layer, agent delegation, budget limits, cross-merchant coordination, and MCP integration. Use when the user asks to compare protocols ('AP2 vs ACP', 'which protocol handles budgets?', 'what's the difference between x402 and MPP?', 'show me the landscape'). Use get_protocol_info instead for deep details on a single protocol.

  ConnectorNo auth

• jupiter_executeOrderA

  SAP MCP ServerB

  Execute a signed swap transaction obtained from getOrder and receive execution status. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Connector

  Destructive

  No auth

• mcp_searchA

  Find MCP - Agentage MCP DirectoryA

  Search the agentage MCP directory - a public catalog of Model Context Protocol servers crawled from the official registry - for servers matching a keyword, optionally narrowed by type, category, language, or license. Use this FIRST whenever the user wants to discover, find, compare, or pick an MCP server ("is there an MCP for X", "which MCP servers do Y"). Results are ranked by text relevance to the query first, then by popularity, so the best match is on top. Returns a page of lean cards (slug, title, description, category, transport, match_score - text relevance the ranking is based on, details_url). To read one server's full packages, tools, and install command, call mcp_get with the slug from a result; open a card's details_url for the human detail page. Valid category, language, and license values come from the mcp_categories tool, not from guesswork - call it before filtering and pass its labels verbatim, or the call is rejected. Read-only - never installs or runs anything.

  ConnectorNo auth

• submit_meta_council_feedbackA

  Meta CouncilA

  Report feedback about the META COUNCIL PLATFORM itself — a noticeable performance failure, a lacking/missing capability, a bug, or a UX/docs gap in Meta Council's tools, councils, workflows, or MCP surface. Platform feedback only: do NOT use this for anything about your own business, customers, deals, invoices, or other data Meta Council manages on your behalf — use the relevant business tool for that instead (e.g. create_deal, create_invoice). Use it the moment a tool result, council run, or workflow falls short. Stored per-user and visible only to platform admins — the response returns an id + acknowledgement and submissions cannot be read back. Include machine context (tool name, session id, model) in the context object.

  ConnectorNo auth

• check_urlA

  WatchpupA

  Check any public URL RIGHT NOW: is it up, HTTP status, response time in ms. With kind:"mcp" it instead performs a real JSON-RPC initialize handshake against a streamable-HTTP MCP server endpoint and reports the server’s self-declared name/version/protocol — useful to tell "the MCP server is down" from "my client is misconfigured". Works without an API key (rate limit 30/hour per IP). For continuous monitoring with alerts, use create_monitor.

  ConnectorNo auth

• seo_test_web_mcpA

  mcp-seoA

  Tests a live website or local endpoint for Web MCP enablement: Checks Streamable HTTP (/mcp), Legacy SSE (/sse), discovery manifests (/.well-known/mcp/server-card.json, llms.txt), CORS headers, and provides copy-paste implementation blueprints in 11 programming languages. USAGE GUIDELINES: - Use to test if a web application exposes an agent-accessible Model Context Protocol interface. - Do NOT use for regular HTML search engine optimization; use 'seo_audit_technical' or 'seo_audit_onpage' instead. BEHAVIORAL TRANSPARENCY: - Safe, read-only protocol diagnostic probe. Makes HTTP GET/HEAD requests to standard discovery endpoints. Modifies no files.

  ConnectorNo auth

• explainA

  chpB

  Learn what CHP is and how it works. Pass a topic, or omit to list topics. Topics: what-is-chp, evidence-model, why-a-protocol, governance, agentic-web, evidence-vs-telemetry, chp-vs-mcp, conformance.

  ConnectorNo auth

• jupiter_getQuoteA

  SAP MCP ServerB

  Get an optimally-routed swap quote with full route plan details (Metis engine). SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  ConnectorNo auth

• evaluate_mcpA

  mcp-judgeA

  Call this BEFORE integrating any third-party MCP server: an unreliable or undocumented MCP wastes your tokens and can break your workflow. PAID $0.05 via x402 (USDC micropayment over HTTP 402 — no account or API key needed; on your first call without payment you receive the exact payment requirements, then retry with the X-PAYMENT header). Returns a complete objective quality report on the target: protocol conformance ('initialize' handshake), tool discovery via 'tools/list', per-tool and per-parameter documentation coverage, latency, and a safe functional probe — free tools are actually called, paid tools are only verified to be cleanly declared (MCP Judge never pays). You get a 0-100 score, A-F letter grade, per-criterion breakdown, and a plain-language summary you can act on. Tip: run the FREE quick_check first to get just the grade, and list_criteria to see exactly how scoring works. Objective checks only — no human and no LLM opinion; it does not judge the real-world usefulness or safety of the content. Set 'url' (required) to the target's MCP endpoint (Streamable HTTP), e.g. https://host/mcp.

  ConnectorNo auth

• agoragentic_registerA

  AgoragenticA

  Register as a new agent on Agoragentic. Returns an API key and access to the router-facing authenticated surfaces. If this MCP session is not yet authenticated, the new key is bound to the current session automatically, so authenticated tools work on your very next call. An already-authenticated session keeps its existing key. Persist the key for future sessions — stdio relay: set AGORAGENTIC_API_KEY; remote HTTP: send Authorization: Bearer <key> at initialize, or pass _meta.apiKey per tools/call.

  ConnectorNo auth

• get-protocol-summaryA

  Crinkl Commerce MCPA

  Get a concise explanation of what Crinkl is and how the protocol works. Use this first if you have no prior context about Crinkl. Returns a plain-text overview of the verification pipeline, token types, and settlement model.

  ConnectorNo auth

• free2aitools_select_modelA

  Free2AIToolsA

  Filter the Free2AITools catalog by declared hardware/license metadata and return FNI-ranked candidate entries. USE WHEN you have concrete constraints (VRAM, params, license, context length, local-runnability) and want candidates narrowed by them. Constraints are metadata/heuristic filters over stored fields, NOT verified compatibility analysis, model inference, or model execution; this tool does not decide for you and is not an inference router. The caller is responsible for the final selection. Results are FNI-ranked, never paid placement, with no billing. Read-only, no side effects. Use free2aitools_search for unconstrained keyword discovery, or free2aitools_rank for keyword ranking without metadata filters.

  ConnectorNo auth

• start_hereA

  SaSame MCP Observatory + Gold Rush TownB

  START HERE. SaSame, operated by SASAME S.R.L., continuously observes and measures the Model Context Protocol ecosystem and publishes verifiable evidence and history; the MCP Factory is internal production machinery and an optional product surface behind it. Current new-user path is free Capability Control Beta: use keyless public tools first, then OAuth account tools when you need capability settings, Marketing Missions, beta usage reset, Factory dashboard or exports. audit_mcp remains the free inspection station; resolve_and_run({goal}) remains supporting read-only routing infrastructure. Measurement is status only, never endorsement.

  ConnectorNo auth

• verify_mcp_readyA

  SaSame MCP Observatory + Gold Rush TownB

  Issue a portable, ed25519-signed 'MCP-Ready Certificate' for one MCP server. SaSame, operated by SASAME S.R.L., continuously observes and measures the Model Context Protocol ecosystem and publishes verifiable evidence and history; the MCP Factory is internal machinery and an optional product surface behind it; measurement only, not endorsement. Internally runs the same probes as audit_mcp, but where audit_mcp returns only a grade, this returns a SIGNED, shareable attestation (canonical JSON + signature) that ANYONE re-verifies OFFLINE with the issuer pubkey (no callback to SaSame), then independently replays the probe-set against the embedded evidence hashes. Honesty caps applied (no verified real content -> grade capped at B; priced endpoints -> delivery UNVERIFIED). The cert is a fact you can check, not a badge we sell.

  ConnectorNo auth