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.

WireTensors

REMOTE · WIRETENSORS.AI

Neutral, verified AI tool reviews — search, compare and get recommendations across 260+ tools.

Available components

0 this week 73 Trust /100

Last scanned (19 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

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 Security46
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 851 tokens (~94/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 76% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (11)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 597 → 851 ▼ functional
    • Tool coverage: 67% → 76% ▲ functional
    • Stability: pass → 0.97 functional
    • New tool “estimate_cost” functional
    • New tool “regional_fit” functional
    • New tool “what_changed” functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 20 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 21 Nov 2026 · Probed https://wiretensors.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=wiretensors.ai CN=WE1,O=Google Trust Services,C=US 16 Oct 2026 14 Jan 2027 ECDSA 256 ECDSA-SHA256 c83f2658303fd2e50e7f9bdce54fcde5
SANs: wiretensors.ai, www.wiretensors.ai, *.www.wiretensors.ai
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 wiretensors.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
wiretensors.ai. No DS 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://wiretensors.ai/mcp Verified 200
http (plaintext) http://wiretensors.ai/mcp Inconclusive 406
MCP tools · 9 exposed · ~653 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 ~48

Side-by-side detail for two tools by slug — pricing, rating, pros/cons, best-for/avoid-if.

NameTypeReqDescription
slug_astringyes–
slug_bstringyes–

No output schema declared.

No examples provided.

estimate_cost ~79

Cost of one tool over a number of months, from its recorded paid tiers. Says plainly when tier prices are not recorded. Per-seat pricing, usage charges and taxes are not modelled.

NameTypeReqDescription
monthsnumber–Period in months, 1-60 (default 12)
slugstringyesThe tool's WireTensors slug

No output schema declared.

No examples provided.

get_tool ~54

Full review detail for a single tool by its WireTensors slug (from search_tools results).

NameTypeReqDescription
slugstringyesThe tool's WireTensors slug, e.g. "chatgpt" or "deepseek"

No output schema declared.

No examples provided.

list_categories ~19

All categories tools are grouped into on WireTensors.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

recommend_tool ~107

Get a ranked recommendation for a use case — e.g. "best free coding AI under $20/mo". Filters by category/budget/free-tier and ranks by WireTensors rating.

NameTypeReqDescription
budgetnumber–Max monthly USD budget
categorystring––
free_tierboolean––
limitnumber––
regionstring–Informational only — see the note field in the response for what is and is not actually tracked per-region

No output schema declared.

No examples provided.

regional_fit ~52

Language support, data residency and payment methods for Southeast Asia. Only a minority of tools have been researched; the response says when a tool has not.

NameTypeReqDescription
slugstringyesThe tool's WireTensors slug

No output schema declared.

No examples provided.

search_tools ~182

Search/filter the WireTensors AI tool catalogue. Returns a ranked (by rating) list of tools matching the given filters, with pricing, rating and links. Use get_tool for full detail on one tool.

NameTypeReqDescription
categorystring–e.g. coding, writing, image, video, productivity, seo
free_tierboolean–true = only tools with a free tier
limitnumber–Max results to return (default: all matches)
max_pricenumber–Maximum monthly USD price for the cheapest paid tier
min_ratingnumber–Minimum WireTensors rating, 1-5
origin_countrystring–e.g. "China" — filter by the tool developer's country of origin
qstring–Free-text search across name, tagline, summary, best_for

No output schema declared.

No examples provided.

site_info ~21

Tool count, coverage dates, and what WireTensors is.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

what_changed ~91

Recorded price changes since a date, newest first, optionally for one tool. Price records only; initial_record marks a plan first recorded on that date.

NameTypeReqDescription
limitnumber–Max rows, 1-500 (default 100)
sincestring–Date like 2026-11-01 (default: last 7 days)
slugstring–Only changes for this tool

No output schema declared.

No examples provided.

Install

How do I install the WireTensors MCP server?

WireTensors is a hosted endpoint at https://wiretensors.ai/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 · wiretensors.ai

# add to Claude Code
claude mcp add --transport http ai-wiretensors-wiretensors 'https://wiretensors.ai/mcp'
Common questions

What is the WireTensors MCP server?

WireTensors is an MCP server listed in the public MCP registry as ai.wiretensors/wiretensors. Neutral, verified AI tool reviews, search, compare and get recommendations across 260+ tools. This page covers its hosted endpoint (https://wiretensors.ai/mcp).

Is the WireTensors MCP server safe to use?

WireTensors scores 73 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 WireTensors MCP server expose?

WireTensors exposes 9 tools: search_tools, get_tool, compare_tools, recommend_tool, estimate_cost, and 4 more. Their descriptions and schemas cost roughly 653 tokens of context every time the server is loaded.

Does the WireTensors MCP server require authentication?

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

Is the WireTensors MCP server still maintained?

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

What did VerifyMCP test on the WireTensors MCP server?

VerifyMCP ran 11 checks on WireTensors, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about WireTensors: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.