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.

API operation

REMOTE · SPEC.BESTSMARTGOODS.COM

Read one operation from a public OpenAPI document: method, path, and required fields.

72 Trust /100

Last scanned (3 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 5 Nov 2026.

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 Security74
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 208 tokens (~208/item across 1 items; 1 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 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

Unverified: 1 category

A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

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 72

    First indexed and scored.

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://spec.bestsmartgoods.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.bestsmartgoods.com CN=Actalis Domain Validated TLS Server RSA CA 2025,O=Actalis S.p.A.,L=Ponte San Pietro,ST=Bergamo,C=IT 31 Oct 2026 18 May 2027 RSA 2048 SHA256-RSA 683d9e2088fa8d1c55b67b13e6474d2f
SANs: *.bestsmartgoods.com, bestsmartgoods.com
CN=Actalis Domain Validated TLS Server RSA CA 2025,O=Actalis S.p.A.,L=Ponte San Pietro,ST=Bergamo,C=IT (CA) CN=Actalis TLS Server RSA Root CA 2025,O=Actalis S.p.A.,C=IT 7 Jul 2025 5 Jul 2035 RSA 4096 SHA512-RSA 440e10626d31db911f1cf5a145e00367
CN=Actalis TLS Server RSA Root CA 2025,O=Actalis S.p.A.,C=IT (CA) CN=Actalis Authentication Root CA,O=Actalis S.p.A./03358520967,L=Milan,C=IT 7 Aug 2025 22 Sept 2030 RSA 4096 SHA512-RSA 2328b3ed98429c6559985f3daa3c6e04
CN=Actalis Domain Validation Server CA G3,O=Actalis S.p.A.,L=Ponte San Pietro,ST=Bergamo,C=IT (CA) CN=Actalis Authentication Root CA,O=Actalis S.p.A./03358520967,L=Milan,C=IT 6 Jul 2020 22 Sept 2030 RSA 4096 SHA256-RSA 12737797a315886dfeb76c7e6a5a0354

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of spec.bestsmartgoods.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
bestsmartgoods.com. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://spec.bestsmartgoods.com/mcp Verified 200
http (plaintext) http://spec.bestsmartgoods.com/mcp HTTPS enforced 301 https://spec.bestsmartgoods.com/mcp
MCP tools · 1 exposed · ~208 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
lookup_operation ~208

Read one operation from a public OpenAPI or Swagger JSON document, or from a simple YAML document. Returns the method, path, operation id, summary, and required parameter and body fields. Send the document URL and a short intent, for example create a pet. The best text match is returned. A private address, a login wall, or a document with no matching operation is not charged. The first 5 successful reads each UTC day from one network address are free and need no key. After the 5, send X-API-Key. A key call costs 0.04 credit when an operation is returned. Do not send a URL on a private network. Key: https://firm.bestsmartgoods.com/signup

NameTypeReqDescription
querystringyesWhat the agent wants to do, for example create a pet. Matched against the method, path, operation id, and summary.
urlstringyesPublic http or https URL of an OpenAPI JSON or simple YAML document.

No output schema declared.

No examples provided.

Install

How do I install the API operation MCP server?

API operation is a hosted endpoint at https://spec.bestsmartgoods.com/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 · spec.bestsmartgoods.com

# add to Claude Code
claude mcp add --transport http ladanyin-api-operation 'https://spec.bestsmartgoods.com/mcp'
Common questions

What is the API operation MCP server?

API operation is an MCP server listed in the public MCP registry as io.github.ladanyin/api-operation. Read one operation from a public OpenAPI document: method, path, and required fields. This page covers its hosted endpoint (https://spec.bestsmartgoods.com/mcp).

Is the API operation MCP server safe to use?

API operation scores 72 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 API operation MCP server expose?

API operation exposes 1 tool: lookup_operation. Their descriptions and schemas cost roughly 208 tokens of context every time the server is loaded.

Does the API operation MCP server require authentication?

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

Is the API operation MCP server still maintained?

API operation 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.