Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

EffectHub

REMOTE · EFFECTHUB.NET

Search and compare 3,000+ checked AI tools: pricing, liveness, Effect and Trust scores.

Available components

+4 this week 83 Trust /100

Last scanned (1 hour ago)

Scores higher than 87% of remote servers

Reachable. Last reached 5 Nov 2026.

Category AI and Machine Learning

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 703 tokens (~175/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
  • Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://effecthub.net/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=effecthub.net CN=WE1,O=Google Trust Services,C=US 14 Oct 2026 12 Jan 2027 ECDSA 256 ECDSA-SHA256 3a83524a64d90bef130182398e103c51
SANs: effecthub.net, *.effecthub.net
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of effecthub.net. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
net. present 37331 13 Verified
effecthub.net. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=2592000
content-security-policy default-src 'self'; base-uri 'none'; object-src 'none'; frame-ancestors 'none'; frame-src 'none'; form-action 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self'; connect-src 'self'; worker-src 'self'; media-src 'self'; manifest-src 'self'; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy accelerometer=(), autoplay=(), browsing-topics=(), camera=(), display-capture=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), publickey-credentials-get=(), screen-wake-lock=(), usb=(), xr-spatial-tracking=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://effecthub.net/api/mcp Verified 200
http (plaintext) http://effecthub.net/api/mcp HTTPS enforced 301 https://effecthub.net/api/mcp
MCP tools · 4 exposed · ~488 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare_tools ~81

Two EffectHub tool cards side by side — pricing, scores, platforms, API, liveness — plus the differences in plain sentences. When EffectHub has a researched head-to-head page for the pair, comparison_url links to it.

NameTypeReqDescription
astringyesSlug of the first tool.
bstringyesSlug of the second tool.
NameTypeReqDescription
aobjectyes–
attributionstringyes–
bobjectyes–
comparison_urlstring|nullyes–
highlightsarrayyes–

No examples provided.

get_tool ~97

Everything public on one EffectHub tool card: what it does, category, pricing model and entry price, Effect score, Trust score, platforms, whether it is still alive and when that was last checked, and the card URL. Takes the tool's slug (from search_tools, or the last part of https://effecthub.net/ai/{slug}).

NameTypeReqDescription
slugstringyesThe tool's slug, e.g. "cursor".
NameTypeReqDescription
attributionstringyes–
toolobjectyes–

No examples provided.

list_alternatives ~88

Tools that do the same job as the given one. Alternatives our research named for this tool come first (basis "researched"), then live tools from the same category (basis "category"). Discontinued tools are left out.

NameTypeReqDescription
limitinteger–How many tools to return (1-20, default 10).
slugstringyesThe tool to find alternatives for.
NameTypeReqDescription
alternatives_urlstring|nullyes–
attributionstringyes–
countintegeryes–
resultsarrayyes–
toolobjectyes–

No examples provided.

search_tools ~222

Search the EffectHub catalog of AI tools by product name, job to be done ("transcribe interviews") or category ("video editing"). Optionally narrow by task slug, category slug or pricing model. Returns published, live tools with pricing, Effect score and a link to each card on effecthub.net.

NameTypeReqDescription
categorystring–Optional category slug, as in https://effecthub.net/ai-tools/{slug}. A top-level category includes its subcategories; matched on each tool's primary category.
limitinteger–How many tools to return (1-20, default 10).
pricingstring–Optional pricing model: free, freemium, free_trial, paid or contact (sales-quoted).
querystringyesWhat to look for: a product name, a job, or a category in plain words.
taskstring–Optional task slug, as in https://effecthub.net/ai-for/{task} (e.g. "text-to-speech"). Only tools tagged with it are returned.
NameTypeReqDescription
attributionstringyes–
countintegeryes–
filtersobjectyes–
querystringyes–
resultsarrayyes–
search_urlstringyes–

No examples provided.

Install

How do I install the EffectHub MCP server?

EffectHub is a hosted endpoint at https://effecthub.net/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · effecthub.net

# add to Claude Code
claude mcp add --transport http net-effecthub-catalog 'https://effecthub.net/api/mcp'
Common questions

What is the EffectHub MCP server?

EffectHub is an MCP server listed in the public MCP registry as net.effecthub/catalog. Search and compare 3,000+ checked AI tools: pricing, liveness, Effect and Trust scores. This page covers its hosted endpoint (https://effecthub.net/api/mcp).

Is the EffectHub MCP server safe to use?

EffectHub scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the EffectHub MCP server expose?

EffectHub exposes 4 tools: search_tools, get_tool, list_alternatives, compare_tools. Their descriptions and schemas cost roughly 488 tokens of context every time the server is loaded.

Does the EffectHub MCP server require authentication?

No. We connected to EffectHub without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the EffectHub MCP server still maintained?

EffectHub is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.