Search evidence-backed AI-tool reviews, rankings, use cases, comparisons & toolkits (read-only).
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://mcp.aidemos.com/mcp17 tools · 94msanswerANSWER 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.…ANSWER 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.…
| Parameter | Type | Description |
|---|---|---|
| question | string | The buyer question in natural language, e.g. 'Which document extraction tool best preserves table structure from scanned PDFs?'. Alternative: pass ranking + cr… |
| ranking | string | Ranking slug (skips routing). |
| criterion | string | Criterion slug or exact name (with `ranking`). |
| scenario | string | Optional scenario/condition of interest. |
list_use_casesList published use-case pages (how-to guides): id, title, slug, url, persona, category, updated_at.List published use-case pages (how-to guides): id, title, slug, url, persona, category, updated_at.
| Parameter | Type | Description |
|---|---|---|
| limit | integer | Max items to return. Omit for all. |
| offset | integer | Items to skip (paging). |
list_rankingsList published ranking pages ("best X"): id, title, slug, url, use_case, persona, category, tools_count, winner, tested_as_of, updated_at.List published ranking pages ("best X"): id, title, slug, url, use_case, persona, category, tools_count, winner, tested_as_of, updated_at.
| Parameter | Type | Description |
|---|---|---|
| limit | integer | Max items to return. Omit for all. |
| offset | integer | Items to skip (paging). |
list_toolsList published AI tool pages: id, name, slug, url, domain, personas[], categories[].List published AI tool pages: id, name, slug, url, domain, personas[], categories[].
| Parameter | Type | Description |
|---|---|---|
| limit | integer | Max items to return. Omit for all. |
| offset | integer | Items to skip (paging). |
list_comparesList published head-to-head comparison pages: id, title, slug, url, tool_a, tool_b, personas[], shared_use_cases[], updated_at.List published head-to-head comparison pages: id, title, slug, url, tool_a, tool_b, personas[], shared_use_cases[], updated_at.
| Parameter | Type | Description |
|---|---|---|
| limit | integer | Max items to return. Omit for all. |
| offset | integer | Items to skip (paging). |
list_toolkitsList published toolkit pages (curated bundles): id, title, slug, url, category.List published toolkit pages (curated bundles): id, title, slug, url, category.
| Parameter | Type | Description |
|---|---|---|
| limit | integer | Max items to return. Omit for all. |
| offset | integer | Items to skip (paging). |
list_personasList personas with published-page counts per type {use_cases, rankings, tools, compares, toolkits}. The slugs are valid input for get_persona.List personas with published-page counts per type {use_cases, rankings, tools, compares, toolkits}. The slugs are valid input for get_persona.
No input schema was published for this tool.
list_categoriesList the category vocabulary in use with per-type counts and a source flag ("collection"|"derived"), sorted by total.List the category vocabulary in use with per-type counts and a source flag ("collection"|"derived"), sorted by total.
No input schema was published for this tool.
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 embedd…Search 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 embedd…
| Parameter | Type | Description |
|---|---|---|
| query* | string | Free-text search query. |
| mode | string | Search mode. |
| type | array | Restrict to these kinds (default: all). |
| persona | string | Restrict to items tagged with this persona slug. |
| category | string | Restrict to this category (case-insensitive). |
| limit | integer | Max results (default 20). |
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).Given 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).
| Parameter | Type | Description |
|---|---|---|
| ranking_id* | string | integer | Ranking id (from list_rankings). |
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}].Given a tool id, return the tool {id,name,slug} and every ranking it appears in [{id,title,slug,url,use_case,rank,badge}].
| Parameter | Type | Description |
|---|---|---|
| tool_id* | string | integer | Tool id (from list_tools). |
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.Given a persona slug (from list_personas), return everything tagged with it: persona, use_cases[], rankings[], compares[], toolkits[], tools[]. Mirrors a persona landing page.
| Parameter | Type | Description |
|---|---|---|
| slug* | string | Persona slug, e.g. "students". |
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 fo…Full 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 fo…
| Parameter | Type | Description |
|---|---|---|
| slug* | string | Tool seo_slug, e.g. "affinda" (from list_tools). |
| fields | array | Optional projection: return ONLY these top-level fields (identity id/name/title/slug/url is always included) to control response size. Available: id, name, slu… |
| proof | string | How many proof artifacts to inline. "sample" (default) = up to 6 per tool, spread across distinct criteria so you see breadth; "full" = every artifact; "none"… |
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 th…Full 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 th…
| Parameter | Type | Description |
|---|---|---|
| slug* | string | Ranking slug, e.g. "resume-parsing-api" (from list_rankings). |
| fields | array | Optional projection: return ONLY these top-level fields (identity id/name/title/slug/url is always included) to control response size. Available: id, title, sl… |
| proof | string | How many proof artifacts to inline. "sample" (default) = up to 6 per tool, spread across distinct criteria so you see breadth; "full" = every artifact; "none"… |
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).Full 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).
| Parameter | Type | Description |
|---|---|---|
| slug* | string | Use-case slug (from list_use_cases). |
| fields | array | Optional projection: return ONLY these top-level fields (identity id/name/title/slug/url is always included) to control response size. Available: id, title, sl… |
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), cr…Query 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), cr…
| Parameter | Type | Description |
|---|---|---|
| tool | string | Tool slug or name, e.g. "landing-ai". |
| tools | array | Several tools at once. |
| ranking | string | Ranking page slug — scope cells to the evidence run that published ranking is bound to (exactly what the page renders). |
| scenario | string | Scenario slug, cross-run group tag (e.g. "scanned-research-paper"), or name fragment. |
| criterion | string | Criterion slug or name, e.g. "table extraction". |
| verdict | string | — |
| evidence | string | — |
| limit | integer | Max cells (default 50). |
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 artifac…Evidence-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 artifac…
| Parameter | Type | Description |
|---|---|---|
| tool_a* | string | First tool slug, e.g. "llamaparse". |
| tool_b* | string | Second tool slug, e.g. "landing-ai". |
| criterion | string | Optional: restrict to one criterion. |
17 of 17 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Search evidence-backed AI-tool reviews, rankings, use cases, comparisons & toolkits (read-only).
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.