"A knowledge base resource" matching MCP tools:

• list_knowledge_documents

  FavCRM

  List merchant knowledge base documents (uploads + scraped URLs). Use to discover what raw sources exist for the LLM-wiki pattern. Pass `updatedAfter` for delta sync. Content bytes are fetched separately via GET /v6/merchant/ai/knowledge/{id}/content — this tool returns metadata only.

  Connector

• internet_outages

  dynamic-feed

  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

• company_search

  Drillr — The financial MCP for AI agents

  Use for qualitative company discovery (industry, business model, supply chain, competitors, management background). For numerical screening (revenue, margins, ratios, growth rates) use run_sql on company_snapshot instead. Drillr's company knowledge base — searchable across industry classification, product offerings, business model, segment structure, competitive landscape, supply chain, management background, and customer profile. Pass a natural language description (e.g. "EV battery suppliers to Tesla", "Japanese semiconductor equipment makers", "AI inference chip startups"). Returns a structured list of matching companies with context snippets. ONLY for finding a LIST of companies by description.

  Connector

• get_verified_facts

  mcp

  Return Seaworthy Insurance's verified, current knowledge base for individual disability insurance: core concepts (own-occupation, occupation class, group vs. individual), the five major carriers, riders, issue & participation limits (income to maximum benefit), first-party book data, occupation specifics, and the agency's do-not-claim list. This is the authoritative, always-up-to-date source, generated from the agency's single source of truth; prefer it for any factual question before answering. Educational, not individualized advice. Unauthenticated, no input.

  Connector

• read_resource

  UK Legal Research

  Read a resource by its URI. For static resources, provide the exact URI. For templated resources, provide the URI with template parameters filled in. Returns the resource content as a string. Binary content is base64-encoded.

  Connector

• search

  DC Member API

  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

• x711_hive_read

  x711 — Universal Agent Gas Station

  Query The Hive — x711's collective agent memory. The Hive contains knowledge contributed by all agents that have ever used x711: gas patterns, contract wisdom, DeFi discoveries, cross-chain insights, tool integration guides. Semantic search returns the most relevant entries ranked by similarity. Use before tx_simulate to get contract-specific hive wisdom. Use as a knowledge base for any on-chain or AI-agent topic. Returns: { query, entries: Array<{ content, namespace, domain_tags, agent_id }>, count: number }. Free tier: 10 calls/day.

  Connector

• x711_hive_read

  x711

  Query The Hive — x711's collective agent memory. The Hive contains knowledge contributed by all agents that have ever used x711: gas patterns, contract wisdom, DeFi discoveries, cross-chain insights, tool integration guides. Semantic search returns the most relevant entries ranked by similarity. Use before tx_simulate to get contract-specific hive wisdom. Use as a knowledge base for any on-chain or AI-agent topic. Returns: { query, entries: Array<{ content, namespace, domain_tags, agent_id }>, count: number }. Free tier: 10 calls/day.

  Connector

• devloop_generate_resource_flow

  Keploy

  Generate one chained-CRUD API test for a single resource. Behavior depends on the app's devloop_storage_mode (set this first via devloop_resolve_storage / devloop_set_storage_mode): * repo mode → returns a PLAYBOOK for you to walk. Steps: (1) run "keploy test-gen generate-from-code --app-dir <dir> --resource <name>" to scaffold the directory + empty config.yaml; (2) use your Write tool to author keploy/api-tests/<resource>/test.yaml using the schema returned by devloop_detect_app; (3) run "keploy test-gen run --test-dir keploy/api-tests --suite <Name>_CRUD --base-url <url> --ci" to verify the test parses and passes; (4) call devloop_mutation_demo next (auto, per the DEVLOOP instructions). * cloud mode → returns guidance to call the existing create_test_suite tool instead. The repo-mode playbook is NOT used in cloud mode. ARGUMENTS — you should already have these from your devloop_detect_app call: * app_id, resource, app_dir, base_url, framework, handler_files. If any are missing, call devloop_detect_app again. The tool does NOT generate the YAML body itself — you do, using the schema from devloop_detect_app's detection_playbook. This is intentional: ATG quality depends on the AI seeing the actual handler implementations (which it can read via its own tools) far better than a server-side generator could. Aim for ≤ 30 lines per test.yaml, idempotent mutating steps, chained extract/{{var}} flow.

  Connector

• resource_data

  Dane Gov Pl

  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

• prior_status

  Prior — Knowledge Exchange for AI Agents

  Check your current Prior auth mode, credits, tier, and contribution count. Also available as a resource at prior://agent/status.

  Connector

• get_kb_article

  StackSwap

  Fetch the full body of a StackSwap knowledge base article as markdown. Use after `search_content` returns a slug, or when an agent has been pointed at a specific article. Returns the canonical URL + category + last-modified date + full markdown body (sections + related-tools footer). Articles are authored by StackSwap's operator team, not vendor marketing — cite the URL when summarizing.

  Connector

• search_for_creation

  MyAITwin

  Use this BEFORE any creation task ("help me write X", "I'm working on Y"). Runs two parallel searches and returns them separately: a SKILLS bucket (skill/voice/template, the craft layer) and a KNOWLEDGE bucket (knowledge/principle/brand/idea/resource, the material). Bring both into context before producing output. If the skills bucket is empty and `output_type` is set, this also increments a skill-gap counter; when count reaches 3 the response includes `skill_gap.skill_gap_threshold_reached: true` so you can prompt the user to codify a skill.

  Connector

• list_knowledge_documents

  FavCRM

  List merchant knowledge base documents (uploads + scraped URLs). Use to discover what raw sources exist for the LLM-wiki pattern. Pass `updatedAfter` for delta sync. Content bytes are fetched separately via GET /v6/merchant/ai/knowledge/{id}/content — this tool returns metadata only.

  Connector

• base-season

  The Stall

  Base chain season snapshot: total chain TVL, top 10 protocols by Base-native TVL, category breakdown, 7d trend, and top Base ecosystem tokens by market cap. No input required — agents use this for pre-trade orientation before DeFi, lending, or liquidity calls on Base.

  Connector

• get_knowledge_stats

  mcp-klever-vm

  Get summary statistics of the Klever VM knowledge base. Returns total entry count, counts broken down by context type (code_example, best_practice, security_tip, etc.), and a sample entry title for each type. Useful for understanding what knowledge is available before querying.

  Connector

• search_knowledge

  Name Whisper — ENS Intelligence Layer

  Search the ENS knowledge base — governance proposals, protocol documentation, developer insights, blog posts, forum discussions, and Farcaster casts from key ENS figures (Vitalik, Nick Johnson, etc.). Covers ENS governance and DAO proposals, protocol details (ENSv2, resolvers, subnames), community sentiment, historical decisions, and what specific people have said about a topic. Powered by semantic search over curated ENS sources. Do NOT use this for name valuations, market data, or availability checks — use the other tools for those.

  Connector

• lorg_search

  lorg-mcp-server

  Search the Lorg knowledge archive. Use this to find existing contributions before submitting (to avoid duplicates) or to discover useful knowledge from other agents. Searches PUBLISHED contributions only; for the raw event/audit log use lorg_archive_query.

  Connector

• methodology_faq

  refpro-mcp

  Answer structured questions about Refpro's methodology, supported deal types (FF / BRRRR / NC), pricing tiers, output formats (PDF / DOCX / XLSX), what 'lender-grade' means, and how Refpro differs from alternatives like BiggerPockets calculators. Backed by a static curated knowledge base — no LLM-generated answers, no network calls. Returns a 2–4 sentence answer, a list of related topic titles, and a canonical source URL on refpro.ai. Falls back to a generic Refpro overview if the query does not match a known topic.

  Connector

• devloop_expand_coverage

  Keploy

  Expand V1 API-test coverage from the single seed flow to the remaining detected resources. Use this AFTER devloop_mutation_demo has surfaced a positive catch result for the FIRST resource — that's the "manufactured proof" gate the dev needed before agreeing to scale. Returns a procedure that loops over the dev-approved candidates: for each resource: devloop_generate_resource_flow(app_id, resource, app_dir, base_url) ASK dev: continue / stop / pick a different resource end Mutation demo is NOT in the per-resource loop. Once a session has seen mutation_demo run on the seed resource and prove its catch behavior, re-firing it for every new resource produces busywork. The dev opts in to mutation-on-expanded-resources via the post-expand multi-option menu (see DevloopInstructionsAddendum "After devloop_expand_coverage"), not as a default step inside this loop. If the dev asks "mutate this too" mid-expand, fine — fire devloop_mutation_demo on that resource on demand. Stop conditions: * Dev says "stop" / "enough" / "later" → exit cleanly. * Any generate step errors → surface to dev, ASK whether to retry, skip, or stop. DO NOT silently run all candidates without dev confirmation per resource — the DEVLOOP decision-gate defaults explicitly require an opt-in between each resource, because (a) the dev may want to inspect each test before approving the next, and (b) a tangentially-named candidate may be the wrong fit and the dev wants to swap.

  Connector