"MCP (Model Context Protocol) requirements and selection" matching MCP tools:

• read_docs

  clipkit

  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.)

  Connector

• list_paired_models

  ReliaStats

  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.

  Connector

• verify

  mcp

  Checks x402 protocol conformance for a target service URL: a live 402 probe (well-formed challenge, non-empty accepts, atomic-unit amounts) plus price coherence against the target's own well-known. PAID ($0.10 USDC via x402). This MCP server holds no wallet, so calling this tool returns the upstream payment requirements rather than a result — pay them with your own x402 client, or call the endpoint directly. A signed, permanently published attestation of the same check is available at /midas-ops/attest ($0.50). Does NOT measure output quality, uptime history, or on-chain transaction volume — see the returned scope_note.

  Connector

• jupiter_getPrice

  SAP MCP Server

  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.

  Connector

• request_user_context

  Uwear

  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.

  Connector

• compare_protocols

  intelligence-mcp

  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.

  Connector

• compare_protocols

  Intelligence MCP

  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.

  Connector

• lookup_vendors

  RoloCache

  Search the RoloCache catalog and return matching vendors. All three parameters are optional and combinable. With no parameters, returns all indexed vendors. query: Searches vendor names, tags, and confirmed protocol names all at once. Examples: "hotel", "car rental", "corporate travel", "MCP". Compound phrases work - "car rental" correctly matches vendors tagged "car-rental". protocol: Exact match against confirmed protocol names. Only returns vendors where that protocol has status confirmed_present. Valid values: A2A, ACP, AP2, MCP, MPP, NLWeb, UCP, WebMCP, x402, openai_apps_sdk, proprietary, self_declared_discovery. An unrecognized value returns empty results, not an error. has_agent_interface: Exact match against "true", "false", or "partial". "partial" means some agent-callable surfaces exist but no single self-serve path covers end-to-end workflows. Results only include vendors with real, current scan data. Each result contains vendor_id, vendor_domain, has_agent_interface, confirmed_protocols, tags, and record_url. Call get_vendor() with the vendor_id to get the full routing record including endpoints, auth, and per-protocol notes.

  Connector

• jupiter_executeOrder

  SAP MCP Server

  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

• mcp_search

  Find MCP - Agentage MCP Directory

  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.

  Connector

• agentfarm_agent_info

  Sonnet 5 Agent

  Returns this agent's identity, listed per-task price, MCP endpoint, and access URL. This metadata call does not run the model and does not require a bearer token.

  Connector

• agentfarm_agent_info

  Opus 4.8 Agent

  Returns this agent's identity, listed per-task price, MCP endpoint, and access URL. This metadata call does not run the model and does not require a bearer token.

  Connector

• explain

  chp

  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.

  Connector

• jupiter_getQuote

  SAP MCP Server

  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.

  Connector

• evaluate_mcp

  mcp-judge

  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.

  Connector

• agentfarm_agent_info

  GPT-5.6-sol Agent

  Returns this agent's identity, listed per-task price, MCP endpoint, and access URL. This metadata call does not run the model and does not require a bearer token.

  Connector

• get_site_details

  Not Human Search

  Get the full agentic readiness report for a specific domain: score, category, all 7 signal checks (llms.txt, ai-plugin.json, OpenAPI, structured API, MCP server, robots.txt AI rules, Schema.org), plus any cached llms.txt content and OpenAPI summary. When an exact search_id newly records this organic-result selection, the response also carries an optional record_action_interest opportunity for this domain. Selection alone is never interest and never contacts the provider.

  Connector

• switch_active_org

  Dashform MCP Server

  Set which organization MCP acts on for subsequent tool calls. The selection is verified against your memberships and persists for this connection.

  Connector

• get-protocol-summary

  Crinkl Commerce MCP

  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.

  Connector

• free2aitools_select_model

  Free2AITools

  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.

  Connector