Skip to main content
Glama
261,119 tools. Last updated 2026-07-05 11:02

"A server for finding information about content ranking systems and algorithms" matching MCP tools:

  • Get full details for a specific villa including description, all photos, amenities, house rules, and check-in/check-out times. Call this when the user wants more information about a property found via search_villas.
    Connector
  • Switch between local and remote DanNet servers on the fly. This tool allows you to change the DanNet server endpoint during runtime without restarting the MCP server. Useful for switching between development (local) and production (remote) servers. Args: server: Server to switch to. Options: - "local": Use localhost:3456 (development server) - "remote": Use wordnet.dk (production server) - Custom URL: Any valid URL starting with http:// or https:// Returns: Dict with status information: - status: "success" or "error" - message: Description of the operation - previous_url: The URL that was previously active - current_url: The URL that is now active Example: # Switch to local development server result = switch_dannet_server("local") # Switch to production server result = switch_dannet_server("remote") # Switch to custom server result = switch_dannet_server("https://my-custom-dannet.example.com")
    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
  • The Mirabello Wealth-Protection Atlas — OBJECTIVE per-pillar sub-indices (0-100) for each jurisdiction: tax efficiency, structure strength, residence clarity, crypto clarity, succession certainty, regulatory transparency (international compliance alignment — NOT a secrecy score) and institutional stability (World Bank WGI, where sourced). No composite ranking — weightings depend on client facts; use get_wealth_index for a client-weighted composite. Pass cc for one jurisdiction, omit for all. Includes methodology + a de-risk note. INFORMATION, NOT ADVICE.
    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
  • Get all notes for your account. Notes are automatically decrypted and returned in reverse chronological order. Use them internally for tool chaining but present only human-readable information (titles, content, dates). # fetch_notes ## When to use Get all notes for your account. Notes are automatically decrypted and returned in reverse chronological order. Use them internally for tool chaining but present only human-readable information (titles, content, dates).
    Connector

Matching MCP Servers

  • A
    license
    B
    quality
    D
    maintenance
    An MCP server that allows users to run and visualize systems models using the lethain:systems library, including capabilities to run model specifications and load systems documentation into the context window.
    Last updated
    2
    14
    MIT
  • F
    license
    A
    quality
    B
    maintenance
    An MCP (Model Context Protocol) server that gives AI agents live, structured ad intelligence across Facebook, Google, and Instagram — data that no base model can produce from training alone. Powered by Apify actors. Works with any MCP-compatible client: Cursor, Claude, etc.
    Last updated
    11

Matching MCP Connectors

  • MCP server for social media and content data including social profiles, engagement metrics, content trends, and influencer analytics for AI agents.

  • Anchor a content-creation event to the Knox chain; returns a C2PA-aligned, FRE 902-shaped bundle.

  • Fetch a public HTTPS URL and answer a specific question about its content. Lean mode — no bundle stored. Use when you have a precise question about a web page. For a broad summary, use summarize_url. For multi-document Q&A, use ask_collection instead. Returns: { url, answer, answer_cited: { value, confidence, citations[] }, confidence: "high"|"medium"|"low", truncated } Example prompts: - "What is the refund policy at https://docs.example.com/policy?" - "Look at [URL] and tell me what the delivery terms are." - "Answer this question based on the content of [URL]: [question]."
    Connector
  • Search the web for any topic and get clean, ready-to-use content. Best for: Finding current information, news, facts, people, companies, or answering questions about any topic. Returns: Clean text content from top search results. Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue". Use category:people / category:company to search through Linkedin profiles / companies respectively. If highlights are insufficient, follow up with web_fetch_exa on the best URLs.
    Connector
  • Returns structured information about what the Recursive platform includes: features, AI model details, supported integrations, and what's included at every tier. Use for systematic feature comparison.
    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
  • Find info about notable/historic landmarks, towns, and remarkable sites near a coordinate. USE FOR: - "What's near Predjama Castle?" - "Notable landmarks around Ljubljana center" - "Tell me about places near 46.05, 14.51" - Finding historic, cultural, or geographic summaries for an entire area at once. - DO NOT iterate over the results to query individual items again. - One call is sufficient to answer the user's broad geographic inquiry. Combine the results into a single comprehensive summary for the user immediately. NOT FOR: directions, finding specific cafes/shops, raw geocoding.
    Connector
  • Fetch a public HTTPS URL and answer a specific question about its content. Lean mode — no bundle stored. Use when you have a precise question about a web page. For a broad summary, use summarize_url. For multi-document Q&A, use ask_collection instead. Returns: { url, answer, answer_cited: { value, confidence, citations[] }, confidence: "high"|"medium"|"low", truncated } Example prompts: - "What is the refund policy at https://docs.example.com/policy?" - "Look at [URL] and tell me what the delivery terms are." - "Answer this question based on the content of [URL]: [question]."
    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
  • Use this read-only tool to compare one crypto public company against its current peer group. It returns peer rank, peer percentile, peer score, stressed leverage, risk tier, debt coverage, quality flags, linkbase provenance, and period/source-date context. Parameters: ticker is required and must be one public-company symbol such as COIN, MSTR, MARA, RIOT, HUT, or CLSK; period is optional and only for reproducing a known filing date. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and does not write external systems or access user accounts. Use it when the user asks whether one issuer is better or worse than peers; use covenant_stress for absolute stress, top_stressed for universe-wide ranking, and alpha_signals for opportunity signals.
    Connector
  • Use this read-only tool to compare one crypto public company against its current peer group. It returns peer rank, peer percentile, peer score, stressed leverage, risk tier, debt coverage, quality flags, linkbase provenance, and period/source-date context. Parameters: ticker is required and must be one public-company symbol such as COIN, MSTR, MARA, RIOT, HUT, or CLSK; period is optional and only for reproducing a known filing date. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and does not write external systems or access user accounts. Use it when the user asks whether one issuer is better or worse than peers; use covenant_stress for absolute stress, top_stressed for universe-wide ranking, and alpha_signals for opportunity signals.
    Connector
  • Discover content franchises within a domain. Two modes: pass `tag` for a precise taxonomy match (every game tagged 'co-op'), or pass `query` for free-text SEMANTIC search powered by pgvector embeddings — finding franchises by meaning ('dark atmospheric games about isolation') even when no literal tag matches. Results are verifiable: tag mode carries tag confidence/corroboration, semantic mode carries a similarity score; both carry entity freshness. When to use: an agent wants a domain-scoped shortlist by tag or by intent. Inputs: a domain plus either a tag or a free-text query.
    Connector
  • Return an explainer of paradigm integration — how DRS handles systems with both flows and items via F2I (Flow-to-Item) and I2F (Item-to-Flow) primitives. Use this when the user asks about Valdez-Tanker-style mixed-paradigm systems or 'how do flows and items coexist'. Deterministic text.
    Connector
  • Query vulnerabilities for multiple packages in one call — the primary tool for dependency audits, SBOM scanning, and lockfile triage. Pass an array of {name, ecosystem, version} tuples (up to 1000). Each entry in the response corresponds positionally to the input. Each finding includes CVE aliases for chaining to nist-nvd-mcp-server for CVSS scoring.
    Connector
  • Queries name frequency and rankings in Brazil (IBGE). Features: 1. **Name frequency** (tipo='frequencia'): - Birth frequency by decade - Multiple names separated by comma - Filter by sex and locality 2. **Name ranking** (tipo='ranking'): - Most popular names - Filter by decade, sex, and locality Available decades: 1930-2010 Examples: - Frequency of "Maria": tipo="frequencia", nomes="Maria" - Compare names: tipo="frequencia", nomes="João,José,Pedro" - 2000s ranking: tipo="ranking", decada=2000 - Female names: tipo="ranking", sexo="F" Behavior: read-only and idempotent — a live GET against the public IBGE Nomes (Censo) API. Returns a Markdown table.
    Connector
  • Return the curated list of example quantum algorithms with published resource estimates (qubit count, depth/gate count, source paper URL). Useful for comparing what algorithms need vs. what hardware can deliver.
    Connector