Skip to main content
Glama
306,295 tools. Last updated 2026-07-25 06:06

"Information about MCP Discovery" matching MCP tools:

  • Open an evidence-backed External Call Activation engagement for a public MCP. Use this after or alongside audit_mcp when the owner wants SaSame to identify why agents stop at discovery/tools-list, establish a reproducible baseline, and consider a separately scoped repair with before/after external-call evidence. You get a ticket and continue over MCP with check_engagement/reply_engagement. Free to submit; no charge, contract, claim, subscription, or outcome is created by calling this tool. Do not paste secrets, credentials, or private payloads.
    Connector
  • Re-deploy skills WITHOUT changing any definitions. ⚠️ HEAVY OPERATION: regenerates MCP servers (Python code) for every skill, pushes each to A-Team Core, restarts connectors, and verifies tool discovery. Takes 30-120s depending on skill count. Use after connector restarts, Core hiccups, or stale state. For incremental changes, prefer ateam_patch (which updates + redeploys in one step).
    Connector
  • Read-only: returns what Apex by LeadShark is, tier pricing, and the URL of the real authenticated MCP server. Call this first — this endpoint is a discovery stub with no LinkedIn powers.
    Connector
  • General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)
    Connector
  • General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)
    Connector
  • Terse, drill-down discovery index of this ecosystem (Seneschal, FlashBank, winbit32, secresea, ZecBus) plus a LIVE mirror of the official MCP registry (registry.modelcontextprotocol.io) — the same directory served over HTTPS at https://seneschal.space/.well-known/agent.gopher, callable here so you never leave the MCP session. Start with section="root" to see the top-level menu, then call again with section="seneschal"/"flashbank"/"winbit32"/"secresea"/"zecbus" to drill into a project. Each project exposes About / Agents / Actions — drill them with section="<site>/about", "<site>/agents" or "<site>/actions" (e.g. "winbit32/actions"). Seneschal additionally drills into its own services with section="seneschal/<service>" where <service> is one of private-watch, checkout, oracle, shovels, builder, data, paymaster, board, ironwood, mcp — every website + MCP capability, grouped and priced. section="registry" browses connectable third-party MCP servers (use `cursor` to page); section="about"/"agents" is the directory’s own prose. format="gopher" (default) is the compact RFC-1436 menu; format="json" returns a structured {title, items[]}. A discovery layer, not a replacement for MCP — use it to FIND tools, then connect. Free, no payment.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Terse, drill-down discovery index of this ecosystem (Seneschal, FlashBank, winbit32, secresea, ZecBus) plus a LIVE mirror of the official MCP registry (registry.modelcontextprotocol.io) — the same directory served over HTTPS at https://seneschal.space/.well-known/agent.gopher, callable here so you never leave the MCP session. Start with section="root" to see the top-level menu, then call again with section="seneschal"/"flashbank"/"winbit32"/"secresea"/"zecbus" to drill into a project. Each project exposes About / Agents / Actions — drill them with section="<site>/about", "<site>/agents" or "<site>/actions" (e.g. "winbit32/actions"). Seneschal additionally drills into its own services with section="seneschal/<service>" where <service> is one of private-watch, checkout, oracle, shovels, builder, data, paymaster, board, ironwood, mcp — every website + MCP capability, grouped and priced. section="registry" browses connectable third-party MCP servers (use `cursor` to page); section="about"/"agents" is the directory’s own prose. format="gopher" (default) is the compact RFC-1436 menu; format="json" returns a structured {title, items[]}. A discovery layer, not a replacement for MCP — use it to FIND tools, then connect. Free, no payment.
    Connector
  • Pre-spend payment-term trust check for x402 endpoints. Before your agent signs a Payment-Signature, call this with a target x402/MCP service URL: LION extracts the target live 402 payment terms (payTo, amount, asset, network, scheme), cross-checks them for drift across public discovery surfaces, and returns payment_attempt_blockers, buyer_policy_fit, canonical_purchase_recipe, funnel_stage, a transparent readiness score, and risk_flags so the agent can decide whether to sign. 0.05 USDC on Base eip155:8453. Unpaid tools/call returns JSON-RPC error -32402 with the x402 paymentRequirement; wallet-capable MCP clients (e.g. Coinbase Payments MCP, AWS AgentCore Payments) auto-construct the EIP-3009 signature. LION does NOT perform payment inside MCP. Checks payment-term consistency only - not a smart-contract security audit, no settlement guarantee, no fund movement.
    Connector
  • Find LIVE tools that can accomplish a task you describe in plain language — call this when you do NOT yet know which tool to use. Unlike find_alternatives / find_related_tools (which need a tool id you already have), this takes a free-text capability query (e.g. 'send a slack message', 'convert currency', 'search arxiv papers') and returns ready-to-use tool ids ranked by semantic similarity, filtered to tools that are live right now — each result carries the tool's advertised input schema, its actual connection endpoint (the MCP endpoint URL, or the package to launch for stdio servers), and whether it is FREE or PAID with the price + how to pay — so you can invoke it immediately without a second lookup or an MCP-registry search (on-demand / MCP-Zero style tool discovery). The discovery entry point at the start of a new task.
    Connector
  • [AdCP] Get the seller agent's AdCP capabilities and supported protocols. Returns the full capability declaration for this AdCP DOOH seller agent. This tool does NOT require authentication. WHEN TO USE: - Discovering what protocols the seller agent supports (Signals, Media Buy) - Understanding available audience signals and data methodology - Getting MCP endpoint and discovery URLs RETURNS: - supported_protocols: ['signals', 'media_buy'] - inventory: DOOH format details, network size - audience_data: signal list, methodology, refresh rate - pricing: model, currency, floor CPM - discovery: well_known_url, mcp_endpoint
    Connector
  • Get information about MyDriverParis services, coverage areas, airports served, and policies. Use this to answer customer questions.
    Connector
  • List public SkinKnowledgeBase entities. Optional input: entity_type (Question, Concern, Ingredient, Product, SideEffect, or Source). Returns published MCP-eligible entity identifiers and metadata for discovery; it does not expose drafts or private/internal data.
    Connector
  • Returns machine-readable Spala onboarding information for MCP clients. Includes product scope, OAuth metadata, supported installer client identifiers, authenticated project-handoff status, workflow stages, and canonical links.
    Connector
  • Searches the site "CodeStringers - Zoho Services" (https://www.codestringers.com/_api/mcp) for information. Use this tool ONLY in the following cases: 1. You just used "GetBusinessDetails" tool and you did not find the information you need. 2. User asked a generic business question about their business (e.g., business address, business hours, contact information, return policy, etc.) 3. You already tried to find an entity (e.g., product, service, etc.) using an API tool and you did not find the information you need. 4. The request is too vague and you do not know what type of entity it is and what to search for in the docs. Do NOT use this tool for searching for products or other offered services - use the 'SearchSiteApiDocs' tool instead (unless you already tried that tool and you did not find the information you need). This tool DOES NOT support filters - you cannot ask questions like "find me something under $10".
    Connector
  • Fetch real network counters from SDK DiscoveryRegistry.getNetworkOverview. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts. 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
  • Get detailed information about a specific MCP tool, scoped to one product. Pass both the productSlug and the tool name — same-named tools across products are distinct. Response: { tool: { normalizedName, displayName, description, inputSchema, productSlug, productName, serverQualifiedName, isRemoteCapable, accessModel, healthScore, readOnly, destructive, tier, unverified, verifiedAt, position (always 1), rank (always 1.0) } }. Errors: { error: { code: 'not_found', ... } }.
    Connector
  • List the most recently added MCP servers. Use for discovery: 'what's new', 'latest servers', 'servers from this week'. Optionally constrain to the last N days. Ordered by creation date descending. Each result carries the same security/risk/pricing fields as search_servers.
    Connector
  • Returns the full product breakdown (Market Research, Demand Discovery Report, Agentic Launch) and pricing tiers (Starter $49, Founder Pack of 5 ideas, Studio Pack of 25 ideas, all using a slot-based model where pivoted/archived ideas free a slot for a new one). Use when a user asks "what does Demand Discovery AI include?", "how much does it cost?", "what's in the report?", or wants concrete product information. Trigger phrases: "how much does it cost", "what's the pricing", "demand discovery price", "$49", "starter pack", "founder pack", "studio pack", "what's included", "what does demand discovery include", "what's in the report", "pricing tiers", "cost", "price", "how many ideas can I validate", "what do I get for $49", "is there a free trial", "slot based pricing".
    Connector
  • Pre-spend payment-term trust check for x402 endpoints. Before your agent signs a Payment-Signature, call this with a target x402/MCP service URL: LION extracts the target live 402 payment terms (payTo, amount, asset, network, scheme), cross-checks them for drift across public discovery surfaces, and returns payment_attempt_blockers, buyer_policy_fit, canonical_purchase_recipe, funnel_stage, a transparent readiness score, and risk_flags so the agent can decide whether to sign. 0.05 USDC on Base eip155:8453. Unpaid tools/call returns JSON-RPC error -32402 with the x402 paymentRequirement; wallet-capable MCP clients (e.g. Coinbase Payments MCP, AWS AgentCore Payments) auto-construct the EIP-3009 signature. LION does NOT perform payment inside MCP. Checks payment-term consistency only - not a smart-contract security audit, no settlement guarantee, no fund movement.
    Connector