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.

Tool Offer Agent

Owner verified

REMOTE · TOOLOFFER.KINGANLOGIC.COM

Source-attributed API/MCP offer drafting, revision, readiness assessment and export.

+3 this week 88 Trust /100

Last scanned (16 hours ago)

Scores higher than 95% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

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 Security97
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
  • The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1278 tokens (~182/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Tools include usage examples.Pass
Stability & Change Management47
  • Stability observed for 14 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 (14% 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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 8 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 (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 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.

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

  • 16 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.

  • 14 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.

  • 12 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.

  • 10 Nov 26 +1

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

  • 8 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Stability: unverified → 0.03 ▲ functional
  • 7 Nov 26 81

    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://tooloffer.kinganlogic.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=kinganlogic.com CN=WE1,O=Google Trust Services,C=US 31 Oct 2026 29 Jan 2027 ECDSA 256 ECDSA-SHA256 467f239ae970a97113f1fa43dce546f7
SANs: kinganlogic.com, tooloffer.kinganlogic.com, *.tooloffer.kinganlogic.com
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 secure

Validation of tooloffer.kinganlogic.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
kinganlogic.com. DS published 2371 13 Verified
tooloffer.kinganlogic.com. Verified address RRset verified with the apex keys
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="tool-offer-machine", resource_metadata="https://tooloffer.kinganlogic.com/.well-known/oauth-protected-resource/mcp"

Bearer realm="tool-offer-machine", resource_metadata="https://tooloffer.kinganlogic.com/.well-known/oauth-protected-resource/mcp"
Header Value
strict-transport-security max-age=86400
x-content-type-options nosniff

Protected resource metadata

Document https://tooloffer.kinganlogic.com/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://tooloffer.kinganlogic.com/mcp
Authorisation server https://tooloffer.kinganlogic.com

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://tooloffer.kinganlogic.com/mcp Verified 200
http (plaintext) http://tooloffer.kinganlogic.com/mcp HTTPS enforced 301 https://tooloffer.kinganlogic.com/mcp
MCP tools · 7 exposed · ~1,003 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
assess_offer_readiness ~146

Deterministic assessment of your retained session without revising seller terms. No fetching, inference, FAHCE, approval or payment. Returns a job, not the report: poll get_result for signed readiness JSON plus full human_readable content, or a resumable report manifest. Not seller certification or commercial clearance. Does not revise seller terms, but creates a metered asynchronous job and may retain delivery state.

NameTypeReqDescription
request_idstringyesCaller-generated UUID for this logical operation. Retain it and identical arguments for retries; do not reuse it for different work.
session_idstringyesThe isolated session UUID returned by start_session; use the same client identity.
NameTypeReqDescription
job_idstringyesThe stable job UUID returned by an operation; poll this same job rather than dispatching replacement work.
release_idstringyesRelease identity bound to this asynchronous operation.
session_idstringyesThe isolated session UUID returned by start_session; use the same client identity.
statusstringyesCurrent job state; only complete with assembled verified content means delivery is finished.
{"request_id":"00000000-0000-4000-8000-000000000001","session_id":"00000000-0000-4000-8000-000000000002"}
export_offer ~152

Export your session's saved offer, proposed plan or explicitly incomplete response without inference. Large responses use the agent's resumable manifest; retrieve each indexed part with get_export_part. An export is not publication or certification. Does not revise seller terms, but creates a metered asynchronous job and may retain delivery state.

NameTypeReqDescription
formatstringyesSaved representation to export. Choose incomplete only for an explicitly unfinished record; export does not publish or authorize it.
request_idstringyesCaller-generated UUID for this logical operation. Retain it and identical arguments for retries; do not reuse it for different work.
session_idstringyesThe isolated session UUID returned by start_session; use the same client identity.

No output schema declared.

{"format":"json","request_id":"00000000-0000-4000-8000-000000000001","session_id":"00000000-0000-4000-8000-000000000002"}
get_export_part ~162

Retrieve one existing resumable export part from your session, without inference. Preserve the manifest and verify its hashes; do not claim completion until all parts are received. Does not revise seller terms, but creates a metered asynchronous job and may retain delivery state.

NameTypeReqDescription
export_idstringyesThe 64-character export hash identifier returned in a multipart manifest for this session.
indexintegeryesOne-based part index from the manifest. Retrieve every part and verify hashes before claiming complete delivery.
request_idstringyesCaller-generated UUID for this logical operation. Retain it and identical arguments for retries; do not reuse it for different work.
session_idstringyesThe isolated session UUID returned by start_session; use the same client identity.

No output schema declared.

{"export_id":"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa","index":1,"request_id":"00000000-0000-4000-8000-000000000001","session_id":"00000000-0000-4000-8000-000000000002"}
get_result ~91

Read a job owned by your authenticated client. pending/processing/uncertain is not completion. Poll this same job; do not duplicate an uncertain message. No inference. Polling is metered and may wake queued processing; it is not annotated as a side-effect-free read.

NameTypeReqDescription
job_idstringyesThe stable job UUID returned by an operation; poll this same job rather than dispatching replacement work.

No output schema declared.

{"job_id":"00000000-0000-4000-8000-000000000003"}
get_status ~101

Ask the existing agent for the current offer status without inference. Returns a job; poll get_result. Does not revise seller terms, but creates a metered asynchronous job and may retain delivery state.

NameTypeReqDescription
request_idstringyesCaller-generated UUID for this logical operation. Retain it and identical arguments for retries; do not reuse it for different work.
session_idstringyesThe isolated session UUID returned by start_session; use the same client identity.

No output schema declared.

{"request_id":"00000000-0000-4000-8000-000000000001","session_id":"00000000-0000-4000-8000-000000000002"}
send_message ~285

Send field: value lines, or a JSON-serialized StructuredIntake object in message, a product question, a revision or a drafting command. Intake keys: tool_url, docs (URL string or 1–3 URL strings), customer, pricing, payment, access, invocation; optional job and seller_name. All other values are strings. Optional schema is TOOL_OFFER_INTAKE_V1. Unknown/duplicate keys and invalid values reject the entire update. Card selections are separate. May use bounded operator model quota. Returns a stable job; optional HTTP Prefer: wait=1 through wait=5 waits without redispatch and may include the signed completed result. Otherwise poll get_result. Never resend uncertain work with a new request_id. No payments or FAHCE execution. May overwrite seller fields or rebuild retained drafts; not read-only. Request-ID deduplication is bounded by retained session/job lifetime, not an unqualified retry guarantee.

NameTypeReqDescription
messagestringyesOffer intake, question, revision or supported drafting command as text; JSON intake must be serialized into this string. Real terms require truthful authorization.
request_idstringyesCaller-generated UUID for this logical operation. Retain it and identical arguments for retries; do not reuse it for different work.
session_idstringyesThe isolated session UUID returned by start_session; use the same client identity.

No output schema declared.

{"message":"status","request_id":"00000000-0000-4000-8000-000000000001","session_id":"00000000-0000-4000-8000-000000000002"}
start_session ~66

Create an isolated seven-day offer conversation. Requires a unique request_id; replaying it returns the same session. No model inference.

NameTypeReqDescription
request_idstringyesCaller-generated UUID for this logical operation. Retain it and identical arguments for retries; do not reuse it for different work.

No output schema declared.

{"request_id":"00000000-0000-4000-8000-000000000001"}
Install

How do I install the Tool Offer Agent MCP server?

Tool Offer Agent is a hosted endpoint at https://tooloffer.kinganlogic.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 · tooloffer.kinganlogic.com

# add to Claude Code
claude mcp add --transport http com-kinganlogic-tool-offer-agent 'https://tooloffer.kinganlogic.com/mcp'
Common questions

What is the Tool Offer Agent MCP server?

Tool Offer Agent is an MCP server listed in the public MCP registry as com.kinganlogic/tool-offer-agent. Source-attributed API/MCP offer drafting, revision, readiness assessment and export. This page covers its hosted endpoint (https://tooloffer.kinganlogic.com/mcp). Its publisher has verified ownership with us.

Is the Tool Offer Agent MCP server safe to use?

Tool Offer Agent scores 88 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 Tool Offer Agent MCP server expose?

Tool Offer Agent exposes 7 tools: start_session, send_message, get_status, assess_offer_readiness, export_offer, and 2 more. Their descriptions and schemas cost roughly 1,003 tokens of context every time the server is loaded.

Does the Tool Offer Agent MCP server require authentication?

Yes. Tool Offer Agent asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Tool Offer Agent MCP server still maintained?

Tool Offer Agent 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 Tool Offer Agent MCP server?

VerifyMCP ran 13 checks on Tool Offer Agent, 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.