MCP.Market

Clay Seal MCP server

by clayseal·io.github.clayseal/clayseal·v0.6.2·1 stars

Authorizes MCP tool calls against a session policy, not one call at a time.

B78/100grade B
What users say
No reviews yet
Be the first
Safety scan
B78/100

full report

Adoption
New

1 stars48 downloads/wk

Reviews

Write one

Nobody has reviewed Clay Seal yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Clay Seal tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it

1 medium
  • Code scan204 source files scanned20/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 37 days ago12/15
  • Maintainer identityregistry namespace matches repository owner7/10

Findings (1)

  • mediumeval / new Function usedexec.eval
    clayseal-0.6.2/clayseal/capabilities/monitor/scoring/transformer.py: …) self.model = model.to(device).eval() self.vocab = vocab sel…
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Clay Seal compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
78/100
higher than 57% of 48,243 servers
GitHub stars
1
more than 65% of 28,706 servers
Downloads a week
48
more than 38% of 12,306 servers with a package

Install Clay Seal in Claude Code, Cursor or VS Code

claude mcp add clayseal -- uvx clayseal
Add to Cursor

What the publisher says

From the Clay Seal repository's README, as published. We do not edit it. Read it on GitHub

Clay Seal

<!-- mcp-name: io.github.clayseal/clayseal -->

Incorporating business-process-logic constraints into AI systems.

Your agent has a $1,000 refund ceiling. It issues eleven refunds of $900. Every call is inside the per-refund limit, so every per-call check passes, and $9,900 goes out the door. Nothing that looks at one call at a time can see this.

Clay Seal sits in front of your tools and judges each call against the whole session: the grant, the running totals, where the arguments came from, and what the agent has already done.

Contents

Working on the code? docs/INTEGRATION.md names which modules the shipped gateway actually executes, which is the fastest way to tell the live path from the parts that are not wired in. The decision itself is SessionBroker.authorizelocked in clayseal/capabilities/broker.py; most refusals come from _floor in the same file.

Start here

If you are a coding agent, skip to the deploy runbook.

pip install clayseal
clayseal try

clayseal try takes about a minute. It runs two attacks in front of you and shows the gateway stopping them. There is nothing to configure, no key to get and nothing leaves your machine.

Every verdict there is decided live by the same gateway you would deploy. The picture is generated from a real run by python scripts/rendertrysvg.py, and a test fails if it drifts from what the command prints, so it cannot become a screenshot of something that used to work.

Python 3.10 to 3.14. Two dependencies, cryptography and pyyaml.

On names. The directory is agentauth-capabilities, the package is

clayseal, and the import is clayseal.capabilities. The project was renamed

at 0.6; agentauth still imports as a deprecation shim. See

Naming at the end for the detail.

If you are an agent

Do this in the project you are editing, in order:

clayseal try --fast
clayseal howto
clayseal policy new > policy.yaml
# rename your_* tools; put mailboxes in egress.recipients; then:
clayseal policy lint policy.yaml
clayseal skill --write

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Clay Seal: common questions

Is Clay Seal MCP server safe?
Mostly: it is graded B (78/100). Read the Clay Seal safety report
How do I install Clay Seal?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Clay Seal need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Clay Seal maintained?
The last commit was 58 days ago (2026-09-08). The latest release is v0.6.2.
How does Clay Seal compare with other MCP servers?
safety score 78/100 (higher than 57% of 48,243 servers); github stars 1 (more than 65% of 28,706 servers); downloads a week 48 (more than 38% of 12,306 servers with a package). Full comparison.