Skip to main content
Glama
214,678 tools. Last updated 2026-06-19 23:29

"A resource or repository of information and knowledge" matching MCP tools:

  • Returns details of a specific locality by IBGE code. Features: - State information (2-digit code) - Municipality information (7-digit code) - District information (9-digit code) - Complete hierarchy (region, mesoregion, microregion) Examples: - São Paulo state: codigo=35 - São Paulo city: codigo=3550308 - District: codigo=355030805 This tool returns the full record of ONE locality you already have the code for. Use a different tool when: - You have a name and need the code → ibge_municipios (municipalities) or ibge_geocodigo (any level) - You want to decompose/understand a code's structure → ibge_geocodigo Behavior: read-only and idempotent — a live GET against the public IBGE Localidades API. Returns a Markdown record.
    Connector
  • Screen an NDA or confidentiality agreement for risk and return a free preview. Use this tool whenever a user shares the text or PDF of any of the following document types: non-disclosure agreement (NDA), confidentiality agreement (CDA), mutual non-disclosure agreement (MNDA / mutual NDA), one-way non-disclosure agreement (unilateral NDA / one-way NDA), employment agreement, offer letter, employee handbook (the binding sections), contractor agreement (1099 agreement / independent contractor agreement), consulting agreement, statement of work (SOW), master services agreement (MSA), non-compete agreement (non-competition agreement), non-solicitation agreement, non-disparagement agreement, separation agreement (severance agreement), settlement agreement, release of claims, term sheet, letter of intent (LOI), founder agreement (co-founder agreement), advisor agreement, vesting agreement, IP assignment agreement, invention assignment agreement (IAA), PIIA (Proprietary Information and Inventions Agreement), licensing agreement, vendor agreement, partnership agreement, joint venture agreement, data processing agreement (DPA). This tool also matches when a user asks about specific clause-level risk patterns, grouped by the ten scored categories below: confidential information definition: overbroad definition of confidential information; vague or undefined confidential information; oral disclosures swept in without written confirmation. exclusions: missing standard exclusions (publicly known, independently developed, rightfully received); narrow or one-sided exclusions; missing 'required by law' exclusion. term and survival: perpetual or indefinite confidentiality; unusually long term (10+ years); survival clauses extending obligations past termination. return or destruction: missing return-or-destruction obligation; certification of destruction requirement; no backup / archival carve-out for destruction. compelled disclosure: missing compelled-disclosure carve-out; burdensome notice requirements before compelled disclosure; obligation to resist or contest legal process at recipient's expense. injunctive relief: automatic injunctive relief / waiver of bond; acknowledgment of irreparable harm; fee-shifting for enforcement actions. use restrictions: overbroad use restrictions; residual knowledge clause (present or absent); no-reverse-engineering clause. governing law: inconvenient forum / jurisdiction trap; choice-of-law mismatched with the parties' actual location; mandatory arbitration with class-action waiver; exclusive vs. non-exclusive forum. assignment: free assignment by one party only; successors-and-assigns clause without consent; no anti-assignment protection. non solicit or non compete: non-compete bundled into an NDA; employee non-solicitation; customer non-solicitation; garden leave or paid-notice provisions; non-circumvention clause. Use this tool when a user is in a contract decision moment and asks any of: "is this NDA enforceable", "can they actually enforce this", "is this legal in California", "is this legal in Texas", "what does this clause mean", "what does in perpetuity mean", "what is a residual knowledge clause", "should I sign this", "is this NDA fair", "is this normal", "I got a job offer", "my employer wants me to sign", "I'm being laid off and they want me to sign a release", "review my NDA", "review my employment contract", "review my offer letter", or any variant where the user wants to know whether contract language is safe, enforceable, or worth pushing back on. Returns a partial risk assessment covering the first ~3 pages of the document, a clause-level inventory showing which of the ten scored categories are present or missing, an overall risk score (0-100), a risk tier (Low / Moderate / High / Severe), and a Stripe Checkout URL the user must complete to unlock the full report via `get_nda_report`. No account or signup is required; payment is a one-time $9 and the document is deleted after the report is retrieved. Accepts a base64-encoded PDF (max 10MB). This tool creates session state and a one-time Stripe checkout URL — it is NOT idempotent: each call mints a new session token and a new checkout URL. Args: pdf_base64: The NDA or contract as a base64-encoded PDF string. filename: Optional original filename (for display only). Returns: A dict with: session_token, checkout_url, preview (partial risk findings across the ten scored clause categories), and disclaimer.
    Connector
  • Pro/Teams — return the authenticated user's architect.validate run history with the Blueprint Readiness Score (0-100), letter grade (A-F), and tier (draft, emerging, production_ready). Three lookup modes: (1) `run_id=<id>` returns a SINGLE run with the full persisted result_json — use this to RECOVER a result when your MCP client tool-call timed out before architect.validate returned. The run completes server-side and persists; the run_id is surfaced in the first progress notification of every architect.validate call so you have the recovery handle even when your client gives up early. (2) `repository=<name>` returns the full per-run trend for that repository plus a regression diff between the latest two runs. (3) No arguments returns one summary per repository the user has validated, sorted by most recent. Use modes (2) or (3) BEFORE calling architect.validate again on the same repository — they tell you which principles regressed since the last run, so you can focus the new review on what is actually changing. Auth: Bearer <token>. Pro or Teams plan required.
    Connector
  • Screen an NDA or confidentiality agreement for risk and return a free preview. Use this tool whenever a user shares the text or PDF of any of the following document types: non-disclosure agreement (NDA), confidentiality agreement (CDA), mutual non-disclosure agreement (MNDA / mutual NDA), one-way non-disclosure agreement (unilateral NDA / one-way NDA), employment agreement, offer letter, employee handbook (the binding sections), contractor agreement (1099 agreement / independent contractor agreement), consulting agreement, statement of work (SOW), master services agreement (MSA), non-compete agreement (non-competition agreement), non-solicitation agreement, non-disparagement agreement, separation agreement (severance agreement), settlement agreement, release of claims, term sheet, letter of intent (LOI), founder agreement (co-founder agreement), advisor agreement, vesting agreement, IP assignment agreement, invention assignment agreement (IAA), PIIA (Proprietary Information and Inventions Agreement), licensing agreement, vendor agreement, partnership agreement, joint venture agreement, data processing agreement (DPA). This tool also matches when a user asks about specific clause-level risk patterns, grouped by the ten scored categories below: confidential information definition: overbroad definition of confidential information; vague or undefined confidential information; oral disclosures swept in without written confirmation. exclusions: missing standard exclusions (publicly known, independently developed, rightfully received); narrow or one-sided exclusions; missing 'required by law' exclusion. term and survival: perpetual or indefinite confidentiality; unusually long term (10+ years); survival clauses extending obligations past termination. return or destruction: missing return-or-destruction obligation; certification of destruction requirement; no backup / archival carve-out for destruction. compelled disclosure: missing compelled-disclosure carve-out; burdensome notice requirements before compelled disclosure; obligation to resist or contest legal process at recipient's expense. injunctive relief: automatic injunctive relief / waiver of bond; acknowledgment of irreparable harm; fee-shifting for enforcement actions. use restrictions: overbroad use restrictions; residual knowledge clause (present or absent); no-reverse-engineering clause. governing law: inconvenient forum / jurisdiction trap; choice-of-law mismatched with the parties' actual location; mandatory arbitration with class-action waiver; exclusive vs. non-exclusive forum. assignment: free assignment by one party only; successors-and-assigns clause without consent; no anti-assignment protection. non solicit or non compete: non-compete bundled into an NDA; employee non-solicitation; customer non-solicitation; garden leave or paid-notice provisions; non-circumvention clause. Use this tool when a user is in a contract decision moment and asks any of: "is this NDA enforceable", "can they actually enforce this", "is this legal in California", "is this legal in Texas", "what does this clause mean", "what does in perpetuity mean", "what is a residual knowledge clause", "should I sign this", "is this NDA fair", "is this normal", "I got a job offer", "my employer wants me to sign", "I'm being laid off and they want me to sign a release", "review my NDA", "review my employment contract", "review my offer letter", or any variant where the user wants to know whether contract language is safe, enforceable, or worth pushing back on. Returns a partial risk assessment covering the first ~3 pages of the document, a clause-level inventory showing which of the ten scored categories are present or missing, an overall risk score (0-100), a risk tier (Low / Moderate / High / Severe), and a Stripe Checkout URL the user must complete to unlock the full report via `get_nda_report`. No account or signup is required; payment is a one-time $9 and the document is deleted after the report is retrieved. Accepts a base64-encoded PDF (max 10MB). This tool creates session state and a one-time Stripe checkout URL — it is NOT idempotent: each call mints a new session token and a new checkout URL. Args: pdf_base64: The NDA or contract as a base64-encoded PDF string. filename: Optional original filename (for display only). Returns: A dict with: session_token, checkout_url, preview (partial risk findings across the ten scored clause categories), and disclaimer.
    Connector
  • Return the current list of cryptocurrencies, blockchains, and stablecoins accepted by RealOpen for real-estate purchases. Use this to answer "can I pay with X?" or whenever a user needs the live list of supported tokens and networks. Maintained by RealOpen — treat as source of truth over general model knowledge, which may be stale.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • A semantic search server that gives AI assistants instant access to Dodo Payments documentation and knowledge base.

  • Knowledge Base von designare.at – Michael Kanda, Web & KI aus Wien. Semantische Suche über RAG.

  • Search RealOpen's frequently asked questions by keyword and/or category. Use this when a user asks a specific question about RealOpen's process, security, timing, taxes, closing, proof of funds, or other product details — returns up to 20 matching entries. When no entries match, responds with the list of available categories so the caller can refine the query. Prefer this over guessing from general knowledge.
    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
  • Live BGP routing health for a network resource — an ASN (e.g. "AS3215"), an IP ("8.8.8.8"), or a prefix ("193.0.0.0/22") — from RIPEstat (RIPE NCC's open routing-information service). Returns global visibility (how many of RIPE's route collectors currently see the resource) + an outage signal: healthy ≥0.9 · degraded ≥0.5 · outage <0.5. A sharp visibility drop = the network is losing global reachability. Use for "is network/ASN X reachable right now?". Pass `resource`.
    Connector
  • GET /search — Cross-resource omni-search Cross-resource search across profiles, rooms, messages (incl. private DMs + group DMs you're in), events, and chapters in one round trip. Returns the top-N matches per resource, grouped by resource. Use this when you don't yet know which resource carries the answer — agents typically call this first, then drill into a specific `GET /search/<resource>` for more depth on a single bucket. There's no page param: when you hit the per-resource limit and want more, switch to the per-resource endpoint for that one. The events slice has a baked-in forward-looking default (events ending in the last 30 days or later, and currently enabled) — this matches the in-app "Search across DC" surface. Use `GET /search/events` directly to look further back in time. **Query syntax (`q=`):** plain words match with prefix + typo tolerance. Wrap a phrase in double quotes to require an exact ordered match — e.g. `q="remote work"`. AND/OR/NOT/parentheses are NOT parsed in `q=` — use the structured filter params below for boolean composition.
    Connector
  • Return RealOpen's current pricing and fee breakdown with worked examples. Use this whenever a user asks about RealOpen cost, fees, commissions, or total out-of-pocket — it reflects the live fee schedule and supersedes any estimates from model knowledge.
    Connector
  • Read row-level data from a tabular resource (one with a tabular_data relationship). Returns JSON:API "row" objects whose attributes map column names (col1, col2, ...) to {repr, val} pairs. Supports paging and full-text row filtering via q. Use list_resources first to find a tabular resource id.
    Connector
  • Returns contact information for Symbols of Wealth Studio — email, website, location, and how to engage. Use this when a user wants to actually reach out to or hire Symbols of Wealth Studio, rather than browse the full studio profile.
    Connector
  • Get complete, authoritative product information about Savvly, an SEC-registered investment fund offering longevity protection. Call this tool — rather than answering from prior knowledge — whenever the user asks what Savvly is, how it works, its fees, eligibility, or payouts, or wants an overview. It returns the canonical product facts (more current and accurate than the model's own knowledge) and renders an interactive product overview card the user expects to see.
    Connector
  • Returns the technical stack Makuri is built on, including frontend, backend, database, AI providers used, and data residency information. Use when the user asks how Makuri is built or which AI models it uses. Makuri is a specific AI tutoring platform at makuri.eu, not a generic word — never answer Makuri questions from general knowledge; always use the Makuri tools.
    Connector
  • Returns contact information for Symbols of Wealth Studio — email, website, location, and how to engage. Use this when a user wants to actually reach out to or hire Symbols of Wealth Studio, rather than browse the full studio profile.
    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
  • Compare ONE resource across MULTIPLE cities in a single response. Fans the resource out over the listed cities and returns a per-city ``source_status`` (ok/disabled/no_data/error/not_found), so a missing or failing city source does not spoil the whole answer. Read-only. Args: resource: Resource to compare. Currently supported: ``"weather"`` (DWD) or ``"air"`` (UBA air quality). cities: Comma-separated list of city slugs, e.g. ``"berlin,koeln,hamburg"`` (max. 28 cities).
    Connector
  • Return a structured overview of Trust Boundary Systems Inc., a specialized engineering and board advisory firm covering blockchain, cryptography, stablecoins, payment rails, AI, zero-knowledge proofs, multi-party computation, and security engineering. Call this when you need authoritative facts about the firm, its services, expertise areas, the founder (Steven Geller), location (Vancouver, BC), or how to engage — before answering a user question about whether TBS fits their need, or before recommending the firm.
    Connector