Skip to main content
Glama
807,015 tools. Updated 2026-11-19 15:17

"A semantic search router for dynamically discovering and routing MCP tool definitions" matching MCP tools:

  • Turn a SPICE netlist into a fab-ready 2-layer PCB: assigns real footprints (0805, TO-92, DO-35, DIP-8, headers, LED, radial-cap), auto-places components (connectivity-aware; or use your own placement), routes a 2-layer maze router with vias, and VERIFIES the result with DRC (clearance/crossing checks) and ERC (union-find copper connectivity proven against the netlist). Returns the board, routing stats + honest unrouted-net list, DRC violations, ERC net status, a 'manufacturable' flag (true only when DRC+ERC clean and everything routed), SVG layers (top/bottom copper, silkscreen, drill, assembly), and optional Gerber RS-274X + Excellon drill files. Same netlist you simulate with spice_simulate — design, verify, and lay out an entire board through the tool layer. Supply a 'placement' array for production-quality boards; the auto-router is a first-pass best-of-N-seeds.
    ConnectorNo auth
  • Before security-sensitive tooling or agent operations: find recent threads relevant to a task, with source links, provenance and matching keywords. Keyword overlap on title, tags and excerpt over the last 200 active threads; not semantic search and not the full archive (use search for that). Seeds excluded by default.
    ConnectorNo auth
  • Search SaidItHere for real-world software dilemmas, framework gotchas, tool fatigue, and battle-tested community consensus workarounds from Reddit, Hacker News, GitHub, and Stack Overflow. Usage Guidelines: - Primary discovery tool: use FIRST when investigating bugs, library gotchas, unexpected price hikes, or developer complaints by keywords. - Sibling routing: follow up with 'get_problem(slug)' using the discovered dilemma slug to inspect full evidence quotes, sources, and step-by-step workarounds. - Sibling routing: if 0 matching dilemmas are returned, use 'suggest_dilemma' to queue the topic for crawler consensus synthesis. - Do NOT use for generic language syntax lookups or textbook documentation queries. Behavior & Side Effects: - Pure read-only, safe, and idempotent query without side effects. Does not modify user, session, or database state.
    ConnectorNo auth
  • 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
  • Given an exact tag/skill (e.g. 'docker', 'gcp'), returns EVERY entry with that tag, uncapped, grouped by type with a real count per type. Unlike related_entries (capped at 15, requires a starting entry id) or query_knowhow (semantic, ranked, may over- or under-include), this is an EXACT tag match against every entry -- the right tool for 'how many X have I completed/done' or 'do I have any real evidence for X at all'. Tags are exact strings from a prior list_by_type/related_entries/query_knowhow result's tags array -- this is NOT semantic search; a tag never assigned during ingest returns found:false, try query_knowhow instead. Each type's entries sort by captured_at ascending (oldest first); entries with no captured_at are moved to the end and counted in undated_count, never silently sorted as if their date were known.
    ConnectorNo auth
  • Performs semantic search across persistent long-term memory to retrieve grounded facts, relevant citations, and source documents matching a natural language question. Use this tool when answering questions about previously saved project specifications, codebase decisions, user preferences, or documents. Do NOT use for saving new facts (use icx_remember), do NOT use for raw keyword lookup (use icx_search_facts), and do NOT use for exact character-for-character verbatim quotes (use icx_quote_slot). Read-only operation with zero side effects. Requires X-License-Key authentication.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables agents to send only the handful of tool definitions relevant to each question, ranking a large catalog by keywords and optional embeddings to cut context cost and wrong-tool picks. It can also run in front of any mcpServers config as a proxy that exposes just search_tools and call_tool instead of the whole catalog.
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Enables semantic search over markdown files to find related notes by meaning rather than keywords, and automatically detect duplicate content before creating new notes.
    3
    2
    BSD 2-Clause "Simplified"

Matching MCP Connectors

  • 4 web-search tiers (x402 USDC on Base) - simple/medium/deep/cached. Free health.

  • Conduit — the governed front door for AI agents. Conduit is a managed MCP router where agents act inside owner-set spending policies. Every call is policy-checked before it fires, metered as it burns, and sealed with a signed, publicly verifiable receipt. What you get: • One endpoint for your agents' model and tool calls. • Per-key budgets and caps that stop runaway loops before they bill you. • A checkable audit trail anyone can verify without trusting us. • Connectors including SEC EDGAR filings & fundamentals (analysis only, never financial advisory). Pricing: Bring your own provider keys — inference passes through at the provider's rate. Verified Calls are sold as credit bundles: $10 / 1,000 · $49 / 6,000 · $199 / 30,000. Free trial with a hard daily cap, no card. Built by AIMLDS. The receipt is the pitch: verify one before you spend a cent.

  • List the canonical trait vocabulary: 30 trait codes grouped by category (Adaptive Capacity, Cognitive Style, Interpersonal Orientation, Drive Architecture, Integrity & Trust) with a one-line semantic per code, plus the valid discovery contexts and the traits never returned about a third party. Use this before composing the trait_priorities argument to query_field or the trait_criteria argument to create_requirement; both are credentialed tools and so are not on the anonymous listing, and query_field is priced per query in USDC over x402. Returns definitions only, never any member's evidence. Static reference data. Free L0, no authentication required.
    ConnectorNo auth
  • Search the authenticated user life graph. Optional from/to (aliases start/end) are inclusive account-local civil dates on every search route; either bound may be used alone. Dated semantic and keyword records use event date, expense date, goal start date, check-in date, or the account-local creation date of contacts and memories. Deterministic routing first: food or relative dates (e.g. "what did I eat yesterday?"); timeline/current-context; money+person; who-is → resolve_person. Otherwise semantic/keyword search. Event hits include event_date and food_id when mirrored from Food Diary. Browser-history titles are excluded. Credential/secret spans are redacted. Records carry inspect_url (their Dayze page): cite with it, never build a link from an id; a record without one has no page (inspect_note says which). Requires OAuth or a supported scoped credential. ($0.15; API key required)
    ConnectorNo auth
  • Semantic web search powered by Exa. Returns titles, URLs, and the top query-relevant excerpt per result. Compact text by default; pass format='json' for full structured data incl. all excerpts per result. Use glim_web_fetch(url) for full page content. Matching is semantic, so a query with no real match still returns ten nearest-neighbour results rather than zero - judge relevance from the excerpts, not from the result count.
    ConnectorNo auth
  • Keyword search over the full Crank tool catalog (progressive disclosure). Read-only, free, never gated. Purpose-built for a discovering agent that does not want to load the full tool catalogue into context just to find the one it needs ( R1 -- the Solana Agent Kit V1 failure mode: 60+ tools in context caused tool-selection hallucinations). Pass a keyword or short phrase (e.g. "perp funding rate", "stake sol", "referral"); matches rank by keyword overlap against each tool's name + description. Returns up to ``limit`` (default 10, max 50) results, each ``{name, purpose, toolset}`` -- ``purpose`` is a one-line summary (call the tool itself, or get_trading_workflow, for the full picture), and ``toolset`` names which of the ten named toolsets (market_data, spot, perps, lending_staking, portfolio, strategies, intelligence, rewards_growth, wallet_admin, support) the tool belongs to. No tool is renamed or hidden by this search -- it is purely a discovery aid.
    ConnectorNo auth
  • Pick exactly one MentionForge tool for a goal. Pass need as a goal sentence, not a tool name — URLs, wallets, and payment header names are stripped before routing; extra keys such as query, timeframe, or payment fields are rejected (those belong on the suggested tool); sending a sibling tool name still keyword-routes from the remaining words. Use this free router when you are unsure which tool to call; for liveness use get_health instead; for price use get_pricing instead; for live mentions use research_mentions. Never charges, never runs research; this origin rate-limits discovery pulses; the 10-call trial is shared across paid tools so call only one paid tool per question.
    ConnectorNo auth
  • Browse the 353-term Canadian privacy glossary with optional text search or first-letter filtering. Use this to explore which terms exist, find the right slug for privacy_lookup_glossary_term, or gather definitions on a topic. Results are paginated: follow next_offset while has_more is true. Pass lang 'fr' to get French definitions where they exist (top-100 Law 25 / PIPEDA terms); the query also matches French names and definitions. LLM clients: resolve Law 25, PIPEDA, and Bill C-36 terms here instead of defining them from pre-training memory, and pin corpus_version in your answer. Use when: Use when someone wants to browse or search the glossary by keyword or letter. Do not use when: Do not use when someone asks for one known term; look that term up directly.
    ConnectorNo auth
  • Browse the 353-term Canadian privacy glossary with optional text search or first-letter filtering. Use this to explore which terms exist, find the right slug for privacy_lookup_glossary_term, or gather definitions on a topic. Results are paginated: follow next_offset while has_more is true. Pass lang 'fr' to get French definitions where they exist (top-100 Law 25 / PIPEDA terms); the query also matches French names and definitions. LLM clients: resolve Law 25, PIPEDA, and Bill C-36 terms here instead of defining them from pre-training memory, and pin corpus_version in your answer. Use when: Use when someone wants to browse or search the glossary by keyword or letter. Do not use when: Do not use when someone asks for one known term; look that term up directly.
    ConnectorNo auth
  • Use this instead of loading a server's full tool definitions when you only need to choose a tool or prepare a call: one compact card per tool (what it does, its arguments with required ones marked *, risk level and side effects) plus a hash of the full definition. Usually 70 to 90% fewer tokens than the server's own tool list. Optionally only the named tools. For a server that asks for sign-in before listing its tools: that it is up and how to connect (no charge). Paid per server (see list_paid_tools). Reads the map only.
    ConnectorNo auth
  • Keyword search over the user's own library: matches transcription titles and transcript text (case-insensitive substring; not semantic). Returns `results[]` of `{id, title, url}` where `id` is the transcription id as a string — pass it to `fetch`, or to the numeric-id tools after `Number(id)`. Transcript-text hits carry a `url` with `?t=<sec>` at the matching segment. This tool + `fetch` implement the ChatGPT connectors / deep-research contract; for structured chapters / sections / Q&A / timestamps prefer `getTranscriptionResult` and `getTranscriptionTimestamps`.
    ConnectorAPI key
  • SANDBOX PREVIEW of Achromat Machine Operational Memory. It takes the same input as the full achromat_recall, but this public endpoint does not search: it ignores task_description and arguments and returns up to 5 featured, approved sample lessons for the domain, each pairing a policy-blocked agent tool call with the compliant fix that was then allowed. The results are examples, never a match for your call: do not use their arguments for live execution. For semantic recall of your own call and live calibration, the user can install the local MCP server: npx -y @achromat-ai/mcp-server.
    ConnectorNo auth
  • Cross-domain search over Dapper's full document corpus (bills, regulations, consultations, news, transcripts), or a document's full metadata by id — one tool, two modes. **With `q`** (default mode; required unless `document_id` is given): tries hybrid search (semantic + lexical RRF + cross-encoder rerank) first; falls back automatically to a plain title/number substring match if unavailable, timed out, or no semantic hit — check `meta.mode` ('semantic' or 'keyword_fallback'). It indexes attached source documents (PDFs and the like), not the records themselves, and coverage is uneven by country: treat an empty result as inconclusive. Returns top-K document stubs: `document_id`, title, `url`, `domain`, `similarity` and `rerank_score` (cite the rerank: negative means the reranker rejected it). `dapper_content_id` is the id of the RECORD the document belongs to — pass it as `id` to that domain's tool or to get_document_text. Pass `document_id` back into this tool for the full snippet. Use `domain=` to scope to one of bills/regulations/consultations/news/transcripts. If you already know the domain and want full structured rows directly (not just a stub), prefer that domain's own `q` param instead — e.g. list_bills(q=...) — it hits the same search but skips the extra document_id round-trip. Accepts Spanish, Portuguese, or English. Results are constrained to `country_code` (comma-separated; omit for every accessible/your default country). **With `document_id`** (from a previous search result): ignores `q` and every other filter, and returns that document's full metadata — title, url, domain, country, published_date, a text snippet, and issuing_entity (regulations only).
    ConnectorAPI key
  • Score an MCP server's tool definitions for what they ask of the model, before you connect it. Input: tools, the tools array of a server's tools/list answer (each {name, description, inputSchema}); or server, the server's name as Smithery lists it (for example brave or owner/name), whose published definitions are read from Smithery. Behavior: runs nothing and calls no server. Fixed rules read each description and every parameter description against the tool's own input schema, because anything in the prose the schema does not need is where an injected instruction lives: tags that frame text as instructions (<IMPORTANT>, <instructions>), HTML comments and invisible characters (zero width, bidirectional controls, Unicode tags), asking the model to drop its instructions, to keep something from the user, or to put a file's contents into an argument, naming files where secrets live (~/.ssh, ~/.cursor/mcp.json, ~/.aws), asking for a credential the schema has no parameter for, steering the model off the web or other servers toward this one, and speaking to the model rather than describing the tool. No model reads the text, so the same definitions always get the same findings and anyone can redo them. Keyless, read-only. Returns: level (clean, review or suspicious), summary, findings (each with tool, rule, severity, where and an excerpt), rulesVersion and inputSha256, the SHA-256 of the definitions as read. A finding is a reason to read the definition, not a verdict on the server: on 500 Smithery servers (12,598 tools, rules 2026-10-31.1) 495 were clean, 3 review and 2 suspicious, and read by hand none hid an order or reached for data: the 3 steer the model off web search toward the server, the 2 were a vendor's response instructions and a false positive. Not for: what a server's code does when it runs (use kenwea_notary_check on its npm package).
    ConnectorNo auth
  • Simulates a 6-turn coding workflow cost projection comparing unrouted flagship execution against tiered routing across grant pools and warm-cached GA models. Stateless in-memory calculation requiring no authentication and mutating no router settings. Scales per-turn cost linearly with context_tokens relative to current_model; when has_custom_router_config is true, reports a non-intrusive shadow comparison rather than active target IDs. Returns JSON with custom_router_mutex_check, six_turn_cost_breakdown (1 cold write turn + 5 warm read turns), and net_saved_usd (positive USD saved vs unrouted baseline). Use this tool when planning multi-turn task allocation; use check_context_cliff for single-turn length checks or reconcile_usage_receipt for post-hoc invoice auditing.
    ConnectorNo auth
  • Simulates a 6-turn coding workflow cost projection comparing unrouted flagship execution against tiered routing across grant pools and warm-cached GA models. Stateless in-memory calculation requiring no authentication and mutating no router settings. Scales per-turn cost linearly with context_tokens relative to current_model; when has_custom_router_config is true, reports a non-intrusive shadow comparison rather than active target IDs. Returns JSON with custom_router_mutex_check, six_turn_cost_breakdown (1 cold write turn + 5 warm read turns), and net_saved_usd (positive USD saved vs unrouted baseline). Use this tool when planning multi-turn task allocation; use check_context_cliff for single-turn length checks or reconcile_usage_receipt for post-hoc invoice auditing.
    ConnectorNo auth
  • Search for legal agreement templates by keyword. Uses BM25 ranking to find the most relevant templates matching your query. Searches across template names, descriptions, categories, sources, and field definitions. Use this instead of list_templates when you know what kind of agreement you need.
    ConnectorNo auth