Skip to content

PriorSeal MCP server

io.github.imokokok/priorsealimokokokstreamable-httpv0.2.0Scanned

Bounded authorization and independently verifiable execution evidence for agents.

12 tools: 5 change things and 7 only read.

Tools: 0 delete, 0 irreversible, 5 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the PriorSeal MCP server can do

The PriorSeal MCP server is published by the GitHub account imokokok. It has 12 tools. It can create or change data (5 tools: priorseal_prepare_authorization, priorseal_prepare_controlled_execution, priorseal_accept_authorization, priorseal_observe_execution and 1 more), but cannot delete data. 7 tools only read.

2 tools bring in text other people can write (priorseal_accept_authorization and priorseal_observe_execution).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 11, 2026, version 0.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

12 tools

Changes things 5Claude Code: ask
  • priorseal_accept_authorizationVerify and persist a principal-signed authorization.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • priorseal_observe_executionPersist an observation request for an already-submitted EVM or Solana transaction, then issue evidence when configured observation completes.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • priorseal_prepare_authorizationCanonicalize a bounded authorization and return the exact EIP-712 typed data or Solana message for a human-controlled principal to sign.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • priorseal_prepare_controlled_executionPrepare a bounded authorization together with the deployment capabilities and a safe, explicit handoff plan.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • priorseal_verify_receiptConvenience-verify a PriorSeal receipt with the deployment key registry.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Convenience-verify a PriorSeal receipt with the deployment key registry. Independent local verification remains required for trust decisions.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 7Show 7 read-only tools
  • priorseal_get_authorizationRead an accepted authorization by its identifier.No findings

    Why it is in this group

    • The name "priorseal_get_authorization" says "get": a word for reading.
    Description, as the server wrote it
    Read an accepted authorization by its identifier.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • priorseal_get_capabilitiesRead the live PriorSeal deployment capabilities before constructing a workflow.No findings

    Why it is in this group

    • The name "priorseal_get_capabilities" says "get": a word for reading.
    Description, as the server wrote it
    Read the live PriorSeal deployment capabilities before constructing a workflow.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • priorseal_get_evidenceGet a free x402 purchase handoff for the chain-neutral Evidence API envelope.No findings

    Why it is in this group

    • The name "priorseal_get_evidence" says "get": a word for reading.
    Description, as the server wrote it
    Get a free x402 purchase handoff for the chain-neutral Evidence API envelope. This MCP result never includes the paid envelope itself.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • priorseal_get_evidence_bundleGet a free x402 purchase handoff for the portable receipt evidence bundle.No findings

    Why it is in this group

    • The name "priorseal_get_evidence_bundle" says "get": a word for reading.
    Description, as the server wrote it
    Get a free x402 purchase handoff for the portable receipt evidence bundle. This MCP result never includes the paid bundle itself.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • priorseal_get_fresh_evidence_checkGet a free x402 purchase handoff for a newly signed, read-only chain re-observation of an authorization-bound receipt.No findings

    Why it is in this group

    • The name "priorseal_get_fresh_evidence_check" says "get": a word for reading.
    Description, as the server wrote it
    Get a free x402 purchase handoff for a newly signed, read-only chain re-observation of an authorization-bound receipt.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • priorseal_get_observation_jobRead the durable status of an automatic finality-observation job.No findings

    Why it is in this group

    • The name "priorseal_get_observation_job" says "get": a word for reading.
    Description, as the server wrote it
    Read the durable status of an automatic finality-observation job.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • priorseal_get_receiptRead a signed execution receipt by its identifier.No findings

    Why it is in this group

    • The name "priorseal_get_receipt" says "get": a word for reading.
    Description, as the server wrote it
    Read a signed execution receipt by its identifier.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:06 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://priorseal.xyz/mcp: tools/list returned 12 tools to an anonymous client, including priorseal_prepare_authorization (write), priorseal_prepare_controlled_execution (write), priorseal_accept_authorization (write), priorseal_observe_execution (write), priorseal_verify_receipt (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 added, 2 changed.+2 added~2 changedView diff

Install

Pinned to version 0.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http priorseal https://priorseal.xyz/mcp
claude mcp add --transport http priorseal https://priorseal.xyz/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__priorseal__priorseal_get_capabilities",
      "mcp__priorseal__priorseal_get_authorization",
      "mcp__priorseal__priorseal_get_observation_job",
      "mcp__priorseal__priorseal_get_receipt",
      "mcp__priorseal__priorseal_get_evidence_bundle",
      "mcp__priorseal__priorseal_get_evidence",
      "mcp__priorseal__priorseal_get_fresh_evidence_check"
    ],
    "ask": [
      "mcp__priorseal__priorseal_prepare_authorization",
      "mcp__priorseal__priorseal_prepare_controlled_execution",
      "mcp__priorseal__priorseal_accept_authorization",
      "mcp__priorseal__priorseal_observe_execution",
      "mcp__priorseal__priorseal_verify_receipt"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as priorseal. Review it before you use it.

Capability tags behind 2 rules
  • mcp__priorseal__priorseal_accept_authorization untrusted-input
  • mcp__priorseal__priorseal_observe_execution untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.imokokok/priorseal/verify?hash=7ae5add6b7189430303b47cc23ea12815e361709b3c29f6c0059dc6e7792feaa" | jq -e '.changed == false'

Pinned hash 7ae5add6b718, from Nov 11, 2026, 04:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.imokokok/priorseal/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.imokokok/priorseal
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.imokokok/priorseal.svg)](https://radar.anlyon.com/servers/io.github.imokokok/priorseal)

Source: MCP Registry · repository. Synced Oct 29, 2026, 17:17 UTC.

PriorSeal MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the PriorSeal MCP server safe?

No scan can promise that. What its definitions show: 12 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the PriorSeal MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the PriorSeal MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the PriorSeal MCP server have?

12 tools: 5 write, 7 read. priorseal_prepare_authorization, priorseal_prepare_controlled_execution, priorseal_accept_authorization, priorseal_observe_execution, priorseal_verify_receipt, priorseal_get_capabilities, priorseal_get_authorization, priorseal_get_observation_job and 4 more.

Does the PriorSeal MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the PriorSeal MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the PriorSeal MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 29, 2026. Every change is on this page and in its Atom feed.