181,009 tools. Last updated 2026-06-07 19:53
"IBM MCP Context Forge - Model Context Protocol Gateway Tool" matching MCP tools:
- 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
- Routes a prompt to the best available x711 LLM. No API keys, no rate limits. Use ONLY when you need external LLM help. Never for things you can answer from context. prefer options: - cheap = fastest + cheapest (classification, extraction) - fast = low latency - smart (default) = best reasoning / code Returns: { text: string, model: string, tokens_used: number, prefer: string }Connector
- Initialize a persistent memory context for a conversation or agent session.Connector
- Fetch the next page of a large tool response. Use the nextCursor from _pagination in a previous response. This tool loads data into the context window — prefer the artifact download URL when available.Connector
- Data tool for the current user's saved client context, including client setup status, advertiser profiles, synced account/campaign counts, and any open setup questions. For the user-facing setup UI, prefer render_context_onboarding.Connector
- Generic protective-action guidance for a category of situation (NOT keyed to an individual user's context). For *personalised* advice that takes the user's specific health situation into account (asthma, pregnancy, gas cooker, tube commute, indoor sources), prefer the Clara MCP server's `contextual_advice` tool — it composes Hermes live readings with personal context to give an answer keyed to *this* user, *now*. Use this KB tool only as a fallback or when Clara is not available. Args: situation: One of "high_pollution_day", "commuting", "exercise", "school_run", "indoor_air", "planning_objection", "pregnancy", "child_asthma". Returns practical advice document (markdown).Connector
Matching MCP Servers
- Alicense-qualityCmaintenanceMCP server enabling real-time weather queries via Tavily API and internet usage data by country via MongoDB.Last updatedApache 2.0
- Alicense-qualityCmaintenanceA basic Python implementation of a Model Context Protocol server for educational purposes, using FastAPI and WebSockets.Last updated294MIT
Matching MCP Connectors
Stop re-explaining yourself to Agents. Give it the right context, right when needed.
MCP memory server with shared team workspaces, typed knowledge chunks (decision, finding, convention, state, question, reference), role-based access, and cross-tool support for Claude, Cursor, and Codex. The only MCP memory server built for engineering teams. Features automatic deduplication, two-layer retrieval (LLM KB selection + hybrid vector/BM25/RRF fusion), a web dashboard with knowledge graph visualization, and attribution tracking. Zero server-side LLM costs.
- Get AI industry news — model releases, funding, acquisitions, policy changes, benchmarks. Returns news events with dates and summaries for industry context.Connector
- Search current AI models by price, context window, and capability. Use this for up-to-date model pricing/features you don't reliably know. Prices are USD per 1M tokens. Results are cheapest-input-price first. Args: query: match part of a model name/id (e.g. "haiku", "gpt"). provider: filter to one provider (openai, anthropic, google, xai, mistral, deepseek, groq). max_input_price: only models at or below this USD/1M input price. min_context: only models with at least this context window (tokens). needs_vision: only models that accept images. limit: max results.Connector
- AI-powered company analysis using semantic search over Nordic financial data. Orchestrates multiple searches internally and returns a synthesized narrative answer with source citations. Covers annual reports, quarterly reports, press releases and macroeconomic context for Nordic listed companies. Use this when you want a synthesized answer rather than raw search chunks. For raw data access, use search_filings or company_research instead. For a full due diligence report with AI-planned sections, use the Alfred MCP server: alfred.aidatanorge.no/mcp Args: company: Company name or ticker question: What you want to know about the company model: 'haiku' (default) or 'sonnet'Connector
- Run a read-only SQL query in the project and return the result. Prefer this tool over `execute_sql` if possible. This tool is restricted to only `SELECT` statements. `INSERT`, `UPDATE`, and `DELETE` statements and stored procedures aren't allowed. If the query doesn't include a `SELECT` statement, an error is returned. For information on creating queries, see the [GoogleSQL documentation](https://cloud.google.com/bigquery/docs/reference/standard-sql/query-syntax). Example Queries: -- Count the number of penguins in each island. SELECT island, COUNT(*) AS population FROM bigquery-public-data.ml_datasets.penguins GROUP BY island -- Evaluate a bigquery ML Model. SELECT * FROM ML.EVALUATE(MODEL `my_dataset.my_model`) -- Evaluate BigQuery ML model on custom data SELECT * FROM ML.EVALUATE(MODEL `my_dataset.my_model`, (SELECT * FROM `my_dataset.my_table`)) -- Predict using BigQuery ML model: SELECT * FROM ML.PREDICT(MODEL `my_dataset.my_model`, (SELECT * FROM `my_dataset.my_table`)) -- Forecast data using AI.FORECAST SELECT * FROM AI.FORECAST(TABLE `project.dataset.my_table`, data_col => 'num_trips', timestamp_col => 'date', id_cols => ['usertype'], horizon => 30) Queries executed using the `execute_sql_readonly` tool will have the job label `goog-mcp-server: true` automatically set. Queries are charged to the project specified in the `project_id` field.Connector
- Set ENS resolver records for a name you own. Returns encoded transaction calldata ready to sign and broadcast. Supports address records (ETH, BTC, SOL, etc.), text records (avatar, description, url, social handles, AI agent metadata), content hash (IPFS/IPNS), ENSIP-25 agent-registration records, and ENSIP-26 agent context and endpoint discovery. Multiple records are batched into a single multicall transaction to save gas. Common text record keys: avatar, description, url, email, com.twitter, com.github, com.discord, ai.agent, ai.purpose, ai.capabilities, ai.category. ENSIP-25 support: Pass agentRegistration with registryAddress and agentId to automatically set the standardized agent-registration text record. This creates a verifiable on-chain binding between your ENS name and your agent identity in an ERC-8004 registry. ENSIP-26 support: Pass agentContext to set the agent-context text record (free-form agent description). Pass agentEndpoints with protocol URLs (mcp, a2a, oasf, web) to set agent-endpoint[protocol] discovery records. The returned transaction can be signed and submitted directly using any wallet framework (Coinbase AgentKit, ethers.js, etc.).Connector
- Submit feedback about Hjarni itself — confusing tool descriptions, missing capabilities, unexpected errors, friction, or praise. Use this when something about the MCP server, a tool, or the product behavior is worth flagging to the maintainers. Do NOT use this for the user's own notes or knowledge — those belong in notes-create. Required: category ('bug'|'confusing'|'missing_feature'|'friction'|'praise'|'other'), message (string, what's wrong and ideally what you'd expect instead). Optional: severity ('low'|'medium'|'high', default 'medium'), tool_name (the MCP tool the feedback is about, e.g. 'notes-update'), context (JSON-encoded string with any extra structured data — error excerpts, the arguments you tried, the workflow that broke).Connector
- One endpoint, multiple live sources (chosen by "source" param): base_dex (price/liquidity/volume), token_risk (security/honeypot), defi_yields, wallet_profile, token_holders, base_rpc_read. Payment always $0.005 USDC on Base (even for Ethereum data). Perfect for pre-swap checks, counterparty profiling, market context. Keyless x402. Use with credits for high volume. No API key. [x402 paid tool: GET /api/x402/adaptive-query?src=mcp returns the 402 challenge with the canonical payTo; price 0.005 USDC on Base eip155:8453.]Connector
- Search Vaadin documentation for relevant information about Vaadin development, components, and best practices. Uses hybrid semantic + keyword search. USE THIS TOOL for questions about: Vaadin components (Button, Grid, Dialog, etc.), TestBench, UI testing, unit testing, integration testing, @BrowserCallable, Binder, DataProvider, validation, styling, theming, security, Push, Collaboration Engine, PWA, production builds, Docker, deployment, performance, and any Vaadin-specific topics. When using this tool, try to deduce the correct development model from context: use "java" for Java-based views, "react" for React-based views, or "common" for both. Use get_full_document with file_paths containing the result's file_path when you need complete context.Connector
- Estimate token count + USD cost for a text across every major LLM (GPT-4o, GPT-4o-mini, o1, o1-mini, Claude 3.5 Sonnet/Haiku, Claude 3 Opus, Gemini 1.5 Pro/Flash, Llama 3 70B/8B) in one call. Returns per-model: estimated tokens, context-window fit %, input cost, and roundtrip cost (input+output). Also returns the cheapest and costliest model that fits. Use this before sending a long context to decide which model to route to. One call replaces 11 separate tokenizer lookups.Connector
- Read the contents of a memory file at `/memories/<path>` or list a directory when the path ends with `/`. Optional `view_range: [start, end]` slices a 1-indexed inclusive line range out of the file. Mirrors the `view` verb in Anthropic's context-management-2025-06-27 memory tool spec. When to use: Call when the model running with `betas: ['context-management-2025-06-27']` issues a `view` against its memory directory. Use `/memories/` (trailing slash) to enumerate files; `/memories/notes.md` to read one. Returns a 404 with typed code on missing path.Connector
- Simulate perceptually modelled subtractive mixing of two colours in CIE Lab space (not RGB screen blending). Returns the resulting mixed hex value and its nearest archive match with cultural context. Uses CIE Lab subtractive model for perceptual accuracy. Example: mixing Prussian Blue and Yellow Ochre gives a muted green — the tool identifies which archive colour that green most closely matches.Connector
- Bridge MCP tool registry to A2A format. Shows tool-to-skill mappings.Connector
- Explain what Pathrule CLI (power-user, web-paired) and Pathrule Desktop (GUI) unlock beyond Remote MCP. Call this when the user asks 'is there a better way?', 'why do I need to install something?', wants hook-level automation, or wants to compare surfaces. The response splits the pitch by audience (CLI for terminal-first, Desktop for GUI) and explains the real token-savings angle: hooks fire before every AI tool call and inject context for free, while remote MCP is manual mode where the AI spends tokens on each context fetch.Connector
- 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