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.

io.github.miranttie/agentictrade

REMOTE · AGENTICTRADE.IO

AI service marketplace — agents discover, call, and pay for API services automatically.

Available components

0 this week 85 Trust /100

Last scanned (17 hours ago)

Scores higher than 86% of remote servers

Reachable. Last reached 21 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
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 270 tokens (~54/item across 5 items; 5 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 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 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
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

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

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 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • Endpoint reachability: not serving MCP → reachable ▲ functional
  • 6 Nov 26 +60
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 −60
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 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
  • 26 Aug 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://agentictrade.io/api/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agentictrade.io CN=YE1,O=Let's Encrypt,C=US 15 Oct 2026 13 Jan 2027 ECDSA 256 ECDSA-SHA384 65c03d5c64cde7a05b195ddd9e4568f00fe
SANs: agentictrade.io
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agentictrade.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
agentictrade.io. 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
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'nonce-F3vqqDziOU8i91R--dea9w'; style-src 'self' 'unsafe-inline' https://rsms.me; font-src 'self' https://rsms.me; img-src 'self' data:; connect-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agentictrade.io/api/v1/mcp Verified 200
http (plaintext) http://agentictrade.io/api/v1/mcp HTTPS enforced 301 https://agentictrade.io/api/v1/mcp
MCP tools · 5 exposed · ~270 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
marketplace_get_agent ~29

Get an agent identity by agent ID.

NameTypeReqDescription
agent_idstringyesThe unique agent ID.

No output schema declared.

No examples provided.

marketplace_get_reputation ~85

Get reputation records for an agent or service. Provide agent_id for agent reputation, service_id for service reputation.

NameTypeReqDescription
agent_idstring–Agent ID to look up reputation for.
periodstring–Period filter, e.g. '2026-03' or 'all-time'.
service_idstring–Service ID to look up reputation for.

No output schema declared.

No examples provided.

marketplace_get_service ~33

Get full details of a single marketplace service by its ID.

NameTypeReqDescription
service_idstringyesThe unique service ID.

No output schema declared.

No examples provided.

marketplace_list_categories ~22

List all service categories with the number of active services in each.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

marketplace_search ~101

Search marketplace services by query string, category, or tags. Returns a list of matching active service listings.

NameTypeReqDescription
categorystring–Filter by service category.
limitinteger–Maximum results to return (default 20, max 100).
offsetinteger–Pagination offset (default 0).
querystring–Free-text search term for service name or description.
tagsarray–Filter by one or more tags.

No output schema declared.

No examples provided.

Install

How do I install the io.github.miranttie/agentictrade MCP server?

io.github.miranttie/agentictrade is a hosted endpoint at https://agentictrade.io/api/v1/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 · agentictrade.io

# add to Claude Code
claude mcp add --transport http miranttie-agentictrade 'https://agentictrade.io/api/v1/mcp'
Common questions

What is the io.github.miranttie/agentictrade MCP server?

io.github.miranttie/agentictrade is an MCP server listed in the public MCP registry as io.github.miranttie/agentictrade. AI service marketplace, agents discover, call, and pay for API services automatically. This page covers its hosted endpoint (https://agentictrade.io/api/v1/mcp).

Is the io.github.miranttie/agentictrade MCP server safe to use?

io.github.miranttie/agentictrade scores 85 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 io.github.miranttie/agentictrade MCP server expose?

io.github.miranttie/agentictrade exposes 5 tools: marketplace_search, marketplace_get_service, marketplace_list_categories, marketplace_get_agent, marketplace_get_reputation. Their descriptions and schemas cost roughly 270 tokens of context every time the server is loaded.

Does the io.github.miranttie/agentictrade MCP server require authentication?

No. We connected to io.github.miranttie/agentictrade without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.miranttie/agentictrade MCP server still maintained?

io.github.miranttie/agentictrade 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 io.github.miranttie/agentictrade MCP server?

VerifyMCP ran 13 checks on io.github.miranttie/agentictrade, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.