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.

Partizan

Owner verified

REMOTE · PARTIZAN.KINGANLOGIC.COM

Look up Base USDC price ceilings for private physical-asset research.

74 Trust /100

Last scanned (15 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 21 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 Security77
  • 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
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability81
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 70 tokens (~70/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Tools include usage examples.Pass
Stability & Change Management7
  • Stability observed for 2 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 (100% 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
  • 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 2 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.

  • 20 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 19 Nov 26 73

    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://partizan.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 30 Sept 2026 29 Dec 2026 ECDSA 256 ECDSA-SHA256 eb28a13fc8388fe30e26fc9b0dc9054c
SANs: kinganlogic.com, partizan.kinganlogic.com, *.partizan.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 partizan.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
partizan.kinganlogic.com. Verified address RRset verified with the apex keys
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
x-content-type-options nosniff

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

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

Read the published Base USDC ceiling for one owner operation. Example: position-refresh returns 350000 atomic units. This lookup is free.

NameTypeReqDescription
operationstringyesPublished Partizan owner operation to price.
NameTypeReqDescription
asset–yes–
max_objectsinteger––
maximum_atomicstringyesAmount in millionths of a USDC.
network–yes–
operationstringyesPublished Partizan owner operation to price.
per_object_atomicstring–Amount in millionths of a USDC.
scheme–yes–
{"operation":"position-refresh"}
Install

How do I install the Partizan MCP server?

Partizan is a hosted endpoint at https://partizan.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 · partizan.kinganlogic.com

# add to Claude Code
claude mcp add --transport http com-kinganlogic-partizan 'https://partizan.kinganlogic.com/mcp'
Common questions

What is the Partizan MCP server?

Partizan is an MCP server listed in the public MCP registry as com.kinganlogic/partizan. Look up Base USDC price ceilings for private physical-asset research. This page covers its hosted endpoint (https://partizan.kinganlogic.com/mcp). Its publisher has verified ownership with us.

Is the Partizan MCP server safe to use?

Partizan scores 74 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 Partizan MCP server expose?

Partizan exposes 1 tool: get_machine_price. Their descriptions and schemas cost roughly 51 tokens of context every time the server is loaded.

Does the Partizan MCP server require authentication?

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

Is the Partizan MCP server still maintained?

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

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