PriorSeal
REMOTE · PRIORSEAL.XYZ
Bounded authorization and independently verifiable execution evidence for agents.
Available components
Last scanned (15 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Security
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
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 520 tokens (~52/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 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 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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 22 Oct 26 0
- Server version: 6338fad255a7c56f2c582499beb3efb26591bae7 → 7a8e65968db1d4c79bca5455c8323fafa357a56f functional
- 21 Oct 26 0
- Server version: d92ae45806d91243d29a38d9d8ffc39876d1a27e → 6338fad255a7c56f2c582499beb3efb26591bae7 functional
- 20 Oct 26 +1
- Server version: 56a187a0-bd1d-4d1e-828d-41ca2af07c29 → d92ae45806d91243d29a38d9d8ffc39876d1a27e functional
- 19 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: a35e70ca7dc10c817d180bc0ce5d89fd4877699b → 56a187a0-bd1d-4d1e-828d-41ca2af07c29 functional
- 18 Oct 26 66
First indexed and scored.
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 22 Oct 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 | 8 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | b793655a45461bfe0ee698d4e5e9f37e |
| 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. | present | 3599, 18130 | 8, 8 | Verified |
| priorseal.xyz. | 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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
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 | Inconclusive | 405 |
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | The complete signed PriorSeal authorization request. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
| mayBroadcastTransaction | – | yes | – |
| nextAction | string | yes | – |
| requiresHumanSignature | boolean | yes | – |
| risk | object | yes | – |
| schema | – | yes | – |
| status | string | yes | – |
| tool | – | yes | – |
No examples provided.
priorseal_get_authorization ~31
Read an accepted authorization by its identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| authorizationId | string | yes | PriorSeal authorization identifier. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
| mayBroadcastTransaction | – | yes | – |
| nextAction | string | yes | – |
| requiresHumanSignature | boolean | yes | – |
| risk | object | yes | – |
| schema | – | yes | – |
| status | string | yes | – |
| 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.
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
| mayBroadcastTransaction | – | yes | – |
| nextAction | string | yes | – |
| requiresHumanSignature | boolean | yes | – |
| risk | object | yes | – |
| schema | – | yes | – |
| status | string | yes | – |
| tool | – | yes | – |
No examples provided.
priorseal_get_evidence_bundle ~37
Export the portable receipt evidence bundle and issuer key-discovery metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| receiptId | string | yes | PriorSeal receipt identifier. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
| mayBroadcastTransaction | – | yes | – |
| nextAction | string | yes | – |
| requiresHumanSignature | boolean | yes | – |
| risk | object | yes | – |
| schema | – | yes | – |
| status | string | yes | – |
| tool | – | yes | – |
No examples provided.
priorseal_get_observation_job ~38
Read the durable status of an automatic finality-observation job.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | PriorSeal observation job identifier. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
| mayBroadcastTransaction | – | yes | – |
| nextAction | string | yes | – |
| requiresHumanSignature | boolean | yes | – |
| risk | object | yes | – |
| schema | – | yes | – |
| status | string | yes | – |
| tool | – | yes | – |
No examples provided.
priorseal_get_receipt ~32
Read a signed execution receipt by its identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| receiptId | string | yes | PriorSeal receipt identifier. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
| mayBroadcastTransaction | – | yes | – |
| nextAction | string | yes | – |
| requiresHumanSignature | boolean | yes | – |
| risk | object | yes | – |
| schema | – | yes | – |
| status | string | yes | – |
| tool | – | yes | – |
No examples provided.
priorseal_observe_execution ~70
Persist an observation request for an already-submitted EVM or Solana transaction, then issue evidence when configured observation completes. This can consume configured Agent credits; send an idempotency key. It never broadcasts a transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | The complete PriorSeal execution-observation request. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
| mayBroadcastTransaction | – | yes | – |
| nextAction | string | yes | – |
| requiresHumanSignature | boolean | yes | – |
| risk | object | yes | – |
| schema | – | yes | – |
| status | string | yes | – |
| 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.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | The complete PriorSeal authorization preparation request. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
| mayBroadcastTransaction | – | yes | – |
| nextAction | string | yes | – |
| requiresHumanSignature | boolean | yes | – |
| risk | object | yes | – |
| schema | – | yes | – |
| status | string | yes | – |
| tool | – | yes | – |
No examples provided.
priorseal_prepare_controlled_execution ~67
Prepare a bounded authorization together with the deployment capabilities and a safe, explicit handoff plan. A human-controlled principal must still sign; this never accepts an authorization, signs, submits, or executes a transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | The complete controlled-execution preparation request. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
| mayBroadcastTransaction | – | yes | – |
| nextAction | string | yes | – |
| requiresHumanSignature | boolean | yes | – |
| risk | object | yes | – |
| schema | – | yes | – |
| status | string | yes | – |
| 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.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | object | yes | Receipt object to verify. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
| mayBroadcastTransaction | – | yes | – |
| nextAction | string | yes | – |
| requiresHumanSignature | boolean | yes | – |
| risk | object | yes | – |
| schema | – | yes | – |
| status | string | yes | – |
| tool | – | yes | – |
No examples provided.
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
claude mcp add --transport http imokokok-priorseal 'https://priorseal.xyz/mcp'
What is the PriorSeal MCP server?
PriorSeal is an MCP server listed in the public MCP registry as io.github.imokokok/priorseal. Bounded authorization and independently verifiable execution evidence for agents. This page covers its hosted endpoint (https://priorseal.xyz/mcp).
Is the PriorSeal MCP server safe to use?
PriorSeal 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 PriorSeal MCP server expose?
PriorSeal exposes 10 tools: priorseal_get_capabilities, priorseal_prepare_authorization, priorseal_prepare_controlled_execution, priorseal_accept_authorization, priorseal_get_authorization, and 5 more. Their descriptions and schemas cost roughly 473 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 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.