protogrid

Search / com.aidemos/catalogue

FutureSmart AI Demos

R0· no sign-in

Search evidence-backed AI-tool reviews, rankings, use cases, comparisons & toolkits (read-only).

v2.0.0 · active · website · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality79good
Trust80of 100
Uptime, 30 days99%
Latency p50208 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "catalogue": {
      "type": "http",
      "url": "https://mcp.aidemos.com/mcp"
    }
  }
}
claude mcp add --transport http catalogue https://mcp.aidemos.com/mcp
[mcp_servers.catalogue]
url = "https://mcp.aidemos.com/mcp"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "catalogue": {
      "type": "remote",
      "url": "https://mcp.aidemos.com/mcp",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "catalogue": {
      "type": "http",
      "url": "https://mcp.aidemos.com/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=catalogue&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLmFpZGVtb3MuY29tL21jcCJ9"
}
{
  "servers": {
    "catalogue": {
      "type": "http",
      "url": "https://mcp.aidemos.com/mcp"
    }
  }
}
{
  "mcpServers": {
    "catalogue": {
      "httpUrl": "https://mcp.aidemos.com/mcp"
    }
  }
}
extensions:
  "catalogue":
    enabled: true
    name: "catalogue"
    type: streamable_http
    uri: "https://mcp.aidemos.com/mcp"
    timeout: 300

Quality 79 / 100good

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene71 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • pass
    tools.description_lengthdescriptions are concise
  • pass
    tools.schemasevery tool has an object input schema
  • fail
    tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
  • fail
    tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: list_rankings (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_tools (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_compares (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
  • pass
    tools.token_costabout 3,045 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stability100 · weight 15
  • pass
    stability.changesno tool changes in 30 days
  • pass
    stability.rug_pullno tool changed its meaning under the same name
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

17 tools, about 3,045 tokens to load them all · tool set 6fd4e69aacf6 · checked 2026-10-20 07:53 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 80 / 100

no-repository
provenance55
liveness100
freshness85
hygiene80

+dns-namespace +website +reachable +uptime-99% ~updated-89d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://mcp.aidemos.com/mcp streamable-httpnoneyes99%208 ms2025-06-182026-10-20

Tools (17)

answerANSWER a buyer question in ONE call: which tool is best at a specific capability, with proof. Returns the resolved verdict our testing team's evidence supports — a named winner FOR THE ASKED CRITERION, every tested tool ranked with a comparable score /5, the CONDITIONS each result holds under (e.g. 'clean tables yes; nested headers no'), dissenting observations preserved as openable links, the tie-break reason, and artifact proof URLs. Answers are materialized from the evidence substrate — the same question returns the same answer. Honestly refuses (coverage: not_tested) when we never tested the topic. Start HERE for any 'which tool is best at X' / 'A or B for X' question; use get_evidence for the raw cells behind it.
compare_toolsEvidence-aligned comparison of two tools, honesty enforced structurally: head_to_head (cells from the SAME test input — provable same-input comparison), related_not_same_input (same dimension, different runs — flagged), and each tool's unique evidence. Built from real observation cells with artifacts, not prose.
get_evidenceQuery the evidence graph: observation cells (tool × test-scenario × criterion) → verdict, score, the researcher's note, and the REAL artifacts (input/output screenshots) that prove it. The ground truth behind every ranking — filter any combination of tool(s), scenario (slug, group tag, or name), criterion, verdict, or evidence state. evidence_state: "verified" = artifact-backed, "observed" = noted without artifact, "scored-only" = number only.
get_personaGiven a persona slug (from list_personas), return everything tagged with it: persona, use_cases[], rankings[], compares[], toolkits[], tools[]. Mirrors a persona landing page.
get_rankingFull ranking detail as a JSON+Markdown envelope: ranked tools (rank/badge/scores), criteria, winner, breakdown (JSON) + verdicts / final take (Markdown). Every ranked tool carries `proof`: real artifact URLs from the exact evidence run this page is bound to, each with the /evidence permalink for the finding it proves — verdict and proof arrive together, no second call needed to cite evidence. `proof.artifact_count` is the true total and `proof.all_findings` is the get_evidence call that returns all of it. null if unknown. Pass `fields` to project to only the keys you need (token-efficient).
get_toolFull tool detail as a JSON+Markdown envelope: identity, pricing, per-feature scores, fit, FAQ, relationships (JSON) + our_take / in-depth review (Markdown). Includes `proof`: real artifact URLs (input/output screenshots, recordings) from the runs that tested it, each with the /evidence permalink for the finding it proves — you can cite evidence from THIS call. null if unknown. Pass `fields` to project to only the keys you need (token-efficient).
get_use_caseFull use-case detail as a JSON+Markdown envelope: step guide, pros/cons, FAQ, tools used (JSON) + the full narrative guide (Markdown, full_md). null if unknown. Pass `fields` to project to only the keys you need (token-efficient).
list_categoriesList the category vocabulary in use with per-type counts and a source flag ("collection"|"derived"), sorted by total.
list_comparesList published head-to-head comparison pages: id, title, slug, url, tool_a, tool_b, personas[], shared_use_cases[], updated_at.
list_personasList personas with published-page counts per type {use_cases, rankings, tools, compares, toolkits}. The slugs are valid input for get_persona.
list_rankingsList published ranking pages ("best X"): id, title, slug, url, use_case, persona, category, tools_count, winner, tested_as_of, updated_at.
list_toolkitsList published toolkit pages (curated bundles): id, title, slug, url, category.
list_toolsList published AI tool pages: id, name, slug, url, domain, personas[], categories[].
list_use_casesList published use-case pages (how-to guides): id, title, slug, url, persona, category, updated_at.
rankings_for_toolGiven a tool id, return the tool {id,name,slug} and every ranking it appears in [{id,title,slug,url,use_case,rank,badge}].
searchSearch the published catalogue across use cases, rankings, tools, comparisons, and toolkits. Returns ranked light refs [{ kind, id, title, slug, url, snippet, score, meta }] — then call get_tool / get_ranking / get_use_case for full detail. `mode`: keyword (substring), semantic (meaning, via embeddings — finds pages by what they cover), or hybrid (default, fuses both). Optional filters: type[], persona, category.
tools_in_rankingGiven a ranking id, return the ranking {id,title,slug} and its ranked tools [{id,name,slug,url,rank,badge}] (badge: Best/Usable/Needs work/Unstable/Failed).

Schemas: list_tools.

Similar MCP servers

Official server.json
{
  "name": "com.aidemos/catalogue",
  "title": "FutureSmart AI Demos",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://mcp.aidemos.com/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "2.0.0",
  "websiteUrl": "https://aidemos.com",
  "description": "Search evidence-backed AI-tool reviews, rankings, use cases, comparisons & toolkits (read-only)."
}