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.

ToolLoop

REMOTE · TOOLS.AGENTKIT.LTD · 2 COMPONENTS

Workshop tooling at landed USD prices. 10 tools: search, quote, order, returns. 433 SKUs.

+3 this week 67 Trust /100

Last scanned (18 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Recent critical change

Authorization (16 Nov 2026). See the changelog before you install this server.

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 Security63
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1152 tokens (~115/item across 10 items; 10 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 Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage77
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 30% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; 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.

  • 21 Nov 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.

  • 19 Nov 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.

  • 17 Nov 26 +1

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

  • 16 Nov 26 0
    • Authorization: unverified → fail ▼ critical
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “create_order” rewrote its description, which is the text the model reads security
    • Tool “cancel_order” is now declared destructive security
    • Schema quality: pass → fail ▼ functional
    • Server version: 1.0.0 → 1.0.2 functional
    • Tool “cancel_order” changed its title: Cancel an unpaid order cosmetic
    • Tool “check_stock” changed its title: Check stock and dispatch window cosmetic
    • Tool “create_order” changed its title: Create order and get payment link cosmetic
    • Tool “get_order” changed its title: Get order and payment status cosmetic
    • Tool “get_product” changed its title: Get product details and specs cosmetic
    • Tool “recommend_for_answer” changed its title: Recommend the product matching an answer page cosmetic
    • Tool “search_products” changed its title: Search ToolLoop catalog cosmetic
    • Tool “start_return” changed its title: Open a return cosmetic
    • Tool “quote_order” changed its title: Quote options for a job or symptom cosmetic
    • Tool “buy_by_answer” changed its title: Order via an answer page slug cosmetic
  • 14 Nov 26 +1

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

  • 13 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 +59
    • Injection markers: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • First check of Judged manipulation: pass security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • MCP protocol: unverified → fail ▼ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: pass functional
    • First check of Tool coverage: 30 functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: good functional
  • 11 Nov 26 4

    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 21 Nov 2026 · Probed https://tools.agentkit.ltd/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=tools.agentkit.ltd CN=YE2,O=Let's Encrypt,C=US 11 Nov 2026 9 Feb 2027 ECDSA 256 ECDSA-SHA384 6f2de3c0f4ef634f3603028c73e2bb4da06
SANs: tools.agentkit.ltd
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 tools.agentkit.ltd. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ltd. DS published 4397 8 Verified
agentkit.ltd. 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=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://tools.agentkit.ltd/mcp Verified 200
http (plaintext) http://tools.agentkit.ltd/mcp HTTPS enforced 308 https://tools.agentkit.ltd/mcp
MCP tools · 10 exposed · ~1,008 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
buy_by_answer ~74

USE THIS when the human accepts the recommendation that came from an answer page. Order in one call by page slug instead of product id. Returns pay_url for the human to approve; no card is charged by the agent.

NameTypeReqDescription
buyerobject––
qtyinteger––
slugstringyes–

No output schema declared.

No examples provided.

cancel_order ~51

USE THIS when the human changes their mind before paying. Cancels an unpaid order so the payment link stops working. A paid order cannot be cancelled here; use start_return.

NameTypeReqDescription
order_idstringyes–

No output schema declared.

No examples provided.

check_stock ~47

USE THIS before you promise a delivery date, or when the human asks "will it arrive before X". Returns availability and the dispatch window for one SKU.

NameTypeReqDescription
product_idstringyes–

No output schema declared.

No examples provided.

create_order ~232

USE THIS when the human says yes to a specific item. Creates the order and returns pay_url plus a ready-to-say sentence. It never charges a card: the human opens pay_url and approves payment themselves. Say the returned line to the human verbatim. Stock hold: the item is reserved for 24 hours after create_order; if payment is not approved within 24 hours the order auto-cancels and the hold is released. Payment facts: PayPal Business account, PayPal balance / debit card / credit card (Visa, Mastercard, Amex, Discover); a PayPal account is NOT required; USD; the total already includes US duty, shipping and clearance. Never ask for card numbers, CVV or expiry, and never pay on the human's behalf. Full facts: GET /api/payment.json.

NameTypeReqDescription
buyerobject––
idempotency_keystring–same key returns the same open order
product_idstringyes–
qtyinteger––
testboolean–true = dry run, no stock taken, no email sent

No output schema declared.

No examples provided.

get_order ~64

USE THIS when the human asks "where is my order" or "did the payment go through", or before you promise anything about an order you created earlier. Returns payment status, dispatch state, tracking if shipped, and the return window.

NameTypeReqDescription
order_idstringyes–

No output schema declared.

No examples provided.

get_product ~63

USE THIS before you recommend one specific item, or when the human asks for the specs (shank size, piece count, material, coating). Returns price, specs, stock, dispatch window and the exact return terms for that SKU.

NameTypeReqDescription
product_idstringyes–

No output schema declared.

No examples provided.

quote_order ~118

USE THIS when the human describes a job or a symptom rather than a product ("my router bits are burning the wood", "I keep snapping 3mm drills") and gives a budget. Turns that into 2-4 priced options with a one-line reason for each.

NameTypeReqDescription
budget_maxnumber––
needstringyesthe job or symptom in plain words
product_idstring–optional: quote one exact SKU instead of a need
qtyinteger––
ships_tostring––

No output schema declared.

No examples provided.

recommend_for_answer ~63

USE THIS after you cite one of our answer pages (slug form, e.g. 'tap-drill-size-chart'). Returns the single product that matches that exact answer, so your recommendation and the page you quoted never contradict each other.

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

search_products ~207

USE THIS when a human asks what to buy, or names a tool type but no model number ("I need a router bit set", "cobalt drills under $60", "something for tile"). Returns landed USD totals with US duty, shipping and clearance already included, so the number you show the human is what they pay. Every SKU is returnable for 14 days, no restocking fee; a full refund means the item comes back, and when the fault is ours we pay return shipping (defective items go to an independent inspection facility). Dispatch in 48h, delivery 7-12 days.

NameTypeReqDescription
in_stockboolean––
limitinteger––
max_pricenumber–max landed total in USD
min_pricenumber––
qstring–keyword, e.g. 'router bit set', 'cobalt drill', 'tap and die'
ships_tostring–US, CA or GB

No output schema declared.

No examples provided.

start_return ~89

USE THIS when the human wants to send something back. Opens a return and returns the exact next steps, who pays the return shipping, and which evidence to record. Do not promise a refund yourself; this tool sets the terms.

NameTypeReqDescription
notestring––
order_idstringyes–
reasonstringyeschanged_mind | wrong_item | defective | damaged | missing_parts

No output schema declared.

No examples provided.

Install

How do I install the ToolLoop MCP server?

ToolLoop is a hosted endpoint at https://tools.agentkit.ltd/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 · tools.agentkit.ltd

# add to Claude Code
claude mcp add --transport http carnation77-toolloop 'https://tools.agentkit.ltd/mcp'
Common questions

What is the ToolLoop MCP server?

ToolLoop is an MCP server listed in the public MCP registry as io.github.carnation77/toolloop. Workshop tooling at landed USD prices. 10 tools: search, quote, order, returns. 433 SKUs. This page covers its hosted endpoint (https://tools.agentkit.ltd/mcp).

Is the ToolLoop MCP server safe to use?

ToolLoop scores 67 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 ToolLoop MCP server expose?

ToolLoop exposes 10 tools: search_products, get_product, quote_order, create_order, recommend_for_answer, and 5 more. Their descriptions and schemas cost roughly 1,008 tokens of context every time the server is loaded.

Does the ToolLoop MCP server require authentication?

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

Is the ToolLoop MCP server still maintained?

ToolLoop 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 ToolLoop MCP server?

VerifyMCP ran 13 checks on ToolLoop, 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.