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.

PriorSeal

REMOTE · PRIORSEAL.XYZ

Seal, observe and verify agentic executions with signed receipts and portable evidence bundles.

Available components

75 Trust /100

Last scanned (15 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

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 Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 685 tokens (~57/item across 12 items; 12 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (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
    • Server version: 390bc2bd4d2f2ec4dd1bc765d1a93908f48bd8f9 → e89b4ad177069f77a80ff232b155cd9da230efb6 functional
  • 19 Nov 26 +1
    • Server version: 2af8ca55e5f0497cbd769d2b4b747aaa9be3751f → 390bc2bd4d2f2ec4dd1bc765d1a93908f48bd8f9 functional
  • 18 Nov 26 0
    • Server version: 117fc887a7e287736346491433c54543bcd8068b → 2af8ca55e5f0497cbd769d2b4b747aaa9be3751f functional
  • 17 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
    • Server version: cfa44e2be1aab4fcf8986c3e947de3019fa75764 → 117fc887a7e287736346491433c54543bcd8068b functional
  • 16 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 21 Nov 2026 · Probed https://priorseal.xyz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=priorseal.xyz CN=WE1,O=Google Trust Services,C=US 14 Nov 2026 12 Feb 2027 ECDSA 256 ECDSA-SHA256 7d8968cd185d824c0e0848ee4ce8bc31
SANs: priorseal.xyz, www.priorseal.xyz, *.www.priorseal.xyz
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 insecure

Validation of priorseal.xyz. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
xyz. DS published 3599, 18130 8, 8 Verified
priorseal.xyz. 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
content-security-policy default-src 'self'; connect-src 'self'; img-src 'self' data:; style-src 'self' 'unsafe-inline'; script-src 'self'; base-uri 'none'; frame-ancestors 'none'; form-action 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy camera=(), geolocation=(), microphone=(), payment=(), usb=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://priorseal.xyz/mcp Verified 200
http (plaintext) http://priorseal.xyz/mcp HTTPS enforced 301 https://priorseal.xyz/mcp
MCP tools · 12 exposed · ~604 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
priorseal_accept_authorization ~63

Verify and persist a principal-signed authorization. This can consume configured Agent credits and changes service state; send an idempotency key. It never signs, submits, or executes a transaction.

NameTypeReqDescription
inputobjectyesThe complete signed PriorSeal authorization request.
NameTypeReqDescription
data–yes–
mayBroadcastTransaction–yes–
nextActionstringyes–
requiresHumanSignaturebooleanyes–
riskobjectyes–
schema–yes–
statusstringyes–
tool–yes–

No examples provided.

priorseal_get_authorization ~31

Read an accepted authorization by its identifier.

NameTypeReqDescription
authorizationIdstringyesPriorSeal authorization identifier.
NameTypeReqDescription
data–yes–
mayBroadcastTransaction–yes–
nextActionstringyes–
requiresHumanSignaturebooleanyes–
riskobjectyes–
schema–yes–
statusstringyes–
tool–yes–

No examples provided.

priorseal_get_capabilities ~23

Read the live PriorSeal deployment capabilities before constructing a workflow.

Input schema present but exposes no named parameters.

NameTypeReqDescription
data–yes–
mayBroadcastTransaction–yes–
nextActionstringyes–
requiresHumanSignaturebooleanyes–
riskobjectyes–
schema–yes–
statusstringyes–
tool–yes–

No examples provided.

priorseal_get_evidence ~49

Get a free x402 purchase handoff for the chain-neutral Evidence API envelope. This MCP result never includes the paid envelope itself.

NameTypeReqDescription
receiptIdstringyesPriorSeal receipt identifier.
NameTypeReqDescription
data–yes–
mayBroadcastTransaction–yes–
nextActionstringyes–
requiresHumanSignaturebooleanyes–
riskobjectyes–
schema–yes–
statusstringyes–
tool–yes–

No examples provided.

priorseal_get_evidence_bundle ~49

Get a free x402 purchase handoff for the portable receipt evidence bundle. This MCP result never includes the paid bundle itself.

NameTypeReqDescription
receiptIdstringyesPriorSeal receipt identifier.
NameTypeReqDescription
data–yes–
mayBroadcastTransaction–yes–
nextActionstringyes–
requiresHumanSignaturebooleanyes–
riskobjectyes–
schema–yes–
statusstringyes–
tool–yes–

No examples provided.

priorseal_get_fresh_evidence_check ~51

Get a free x402 purchase handoff for a newly signed, read-only chain re-observation of an authorization-bound receipt.

NameTypeReqDescription
receiptIdstringyesPriorSeal receipt identifier.
NameTypeReqDescription
data–yes–
mayBroadcastTransaction–yes–
nextActionstringyes–
requiresHumanSignaturebooleanyes–
riskobjectyes–
schema–yes–
statusstringyes–
tool–yes–

No examples provided.

priorseal_get_observation_job ~38

Read the durable status of an automatic finality-observation job.

NameTypeReqDescription
jobIdstringyesPriorSeal observation job identifier.
NameTypeReqDescription
data–yes–
mayBroadcastTransaction–yes–
nextActionstringyes–
requiresHumanSignaturebooleanyes–
riskobjectyes–
schema–yes–
statusstringyes–
tool–yes–

No examples provided.

priorseal_get_receipt ~32

Read a signed execution receipt by its identifier.

NameTypeReqDescription
receiptIdstringyesPriorSeal receipt identifier.
NameTypeReqDescription
data–yes–
mayBroadcastTransaction–yes–
nextActionstringyes–
requiresHumanSignaturebooleanyes–
riskobjectyes–
schema–yes–
statusstringyes–
tool–yes–

No examples provided.

priorseal_observe_execution ~82

Persist an observation request for an already-submitted EVM or Solana transaction, then issue evidence when configured observation completes. A successful metered observation includes its first portable evidence bundle. This can consume configured Agent credits; send an idempotency key. It never broadcasts a transaction.

NameTypeReqDescription
inputobjectyesThe complete PriorSeal execution-observation request.
NameTypeReqDescription
data–yes–
mayBroadcastTransaction–yes–
nextActionstringyes–
requiresHumanSignaturebooleanyes–
riskobjectyes–
schema–yes–
statusstringyes–
tool–yes–

No examples provided.

priorseal_prepare_authorization ~68

Canonicalize a bounded authorization and return the exact EIP-712 typed data or Solana message for a human-controlled principal to sign. This is read-only and never signs, submits, or executes a transaction.

NameTypeReqDescription
inputobjectyesThe complete PriorSeal authorization preparation request.
NameTypeReqDescription
data–yes–
mayBroadcastTransaction–yes–
nextActionstringyes–
requiresHumanSignaturebooleanyes–
riskobjectyes–
schema–yes–
statusstringyes–
tool–yes–

No examples provided.

priorseal_prepare_controlled_execution ~74

Prepare the Seal stage of one Verified Action together with deployment capabilities and a safe handoff plan for Witness, Match, and Review. A human-controlled principal must still sign; this never accepts an authorization, signs, submits, or executes a transaction.

NameTypeReqDescription
inputobjectyesThe complete Verified Action preparation request.
NameTypeReqDescription
data–yes–
mayBroadcastTransaction–yes–
nextActionstringyes–
requiresHumanSignaturebooleanyes–
riskobjectyes–
schema–yes–
statusstringyes–
tool–yes–

No examples provided.

priorseal_verify_receipt ~44

Convenience-verify a PriorSeal receipt with the deployment key registry. Independent local verification remains required for trust decisions.

NameTypeReqDescription
receiptobjectyesReceipt object to verify.
NameTypeReqDescription
data–yes–
mayBroadcastTransaction–yes–
nextActionstringyes–
requiresHumanSignaturebooleanyes–
riskobjectyes–
schema–yes–
statusstringyes–
tool–yes–

No examples provided.

Install

How do I install the PriorSeal MCP server?

PriorSeal is a hosted endpoint at https://priorseal.xyz/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 · priorseal.xyz

# add to Claude Code
claude mcp add --transport http xyz-priorseal-priorseal 'https://priorseal.xyz/mcp'
Common questions

What is the PriorSeal MCP server?

PriorSeal is an MCP server listed in the public MCP registry as xyz.priorseal/priorseal. Seal, observe and verify agentic executions with signed receipts and portable evidence bundles. This page covers its hosted endpoint (https://priorseal.xyz/mcp).

Is the PriorSeal MCP server safe to use?

PriorSeal scores 75 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 PriorSeal MCP server expose?

PriorSeal exposes 12 tools: priorseal_get_capabilities, priorseal_prepare_authorization, priorseal_prepare_controlled_execution, priorseal_accept_authorization, priorseal_get_authorization, and 7 more. Their descriptions and schemas cost roughly 604 tokens of context every time the server is loaded.

Does the PriorSeal MCP server require authentication?

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

Is the PriorSeal MCP server still maintained?

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

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