McpStamp Service Agreement MCP server
io.github.theluckystrike/service-agreementtheluckystrikestreamable-httpv0.23.0Scanned
Freelance service agreements: scope, deliverables, rate, termination, liability cap, clauses.
9 tools: 6 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
6 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.
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 McpStamp Service Agreement MCP server can do
The McpStamp Service Agreement MCP server is published by the GitHub account theluckystrike. It has 9 tools. It can create or change data (6 tools: agreement_create, agreement_update_status, clause_library, agreement_render and 2 more), but cannot delete data. 3 tools only read.
1 tool brings in text other people can write (license_status).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 2026, version 0.23.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.
9 tools
Changes things 6Claude Code: ask
agreement_checklistThe before-you-send-it checklist for one agreement: every missing field is listed, and terms whose absence cuts one way are flagged neutrally -- as written, what the gap means for …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 The before-you-send-it checklist for one agreement: every missing field is listed, and terms whose absence cuts one way are flagged neutrally -- as written, what the gap means for both parties -- such as no termination clause or an uncapped liability. Reads only.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
agreement_createWrite a service agreement between a freelancer and a client before the work starts: the parties, the scope of services, the deliverables, the rate and payment terms, start and end …No findings
Why it is in this group
- The name "agreement_create" says "create": a word for a change.
Description, as the server wrote it Write a service agreement between a freelancer and a client before the work starts: the parties, the scope of services, the deliverables, the rate and payment terms, start and end dates, a termination notice period, a liability cap and the governing jurisdiction. Stores the agreement and returns it rendered as clean Markdown with a signature block. Free tier: 3 active agreements; expiring a finished one frees its slot.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
agreement_renderRender a service agreement ready to send and sign: the parties, the services, the deliverables, the payment terms, the term, termination, liability, jurisdiction, any library claus…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.
Description, as the server wrote it Render a service agreement ready to send and sign: the parties, the services, the deliverables, the payment terms, the term, termination, liability, jurisdiction, any library clauses it carries, and a signature block for both parties. Markdown, or self-contained HTML with print CSS that needs nothing from the network. HTML is a Pro feature. Writes nothing.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
agreement_update_statusMove one agreement exactly one step: draft, sent, signed, expired, stamping the date and an optional note into its history.No findings
Why it is in this group
- The name "agreement_update_status" says "update": a word for a change.
Description, as the server wrote it Move one agreement exactly one step: draft, sent, signed, expired, stamping the date and an optional note into its history. A skipped or backwards step is refused and nothing is written. Expiring a finished engagement frees a free-tier slot.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
clause_libraryList the built-in clause library: intellectual property assignment, mutual confidentiality, late payment interest, kill fee and revision rounds.1 finding
Why it is in this group
- The description's first verb is "list": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "clause_library" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "list": a word for reading.
Description, as the server wrote it List the built-in clause library: intellectual property assignment, mutual confidentiality, late payment interest, kill fee and revision rounds. Each clause is a title plus a body text. Pass an agreement and, on Pro, every body comes back with that agreement's variables filled in. The free tier lists titles and summaries; the full texts are a Pro feature.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
license_activateTurn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle.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.
Description, as the server wrote it Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 3Show 3 read-only tools
agreement_getRead one service agreement in full by SA number or client name: parties, scope, deliverables, rate and payment terms, dates, termination, liability cap, jurisdiction, the clauses i…No findings
Why it is in this group
- The name "agreement_get" says "get": a word for reading.
Description, as the server wrote it Read one service agreement in full by SA number or client name: parties, scope, deliverables, rate and payment terms, dates, termination, liability cap, jurisdiction, the clauses it carries, its status and its status history. Reads only.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
agreement_listList service agreements newest first: parties, status, rate, dates and the clauses each carries.No findings
Why it is in this group
- The name "agreement_list" says "list": a word for reading.
Description, as the server wrote it List service agreements newest first: parties, status, rate, dates and the clauses each carries. Filter by status and by client. An agreement is active until it is expired; the free tier holds 3 active agreements.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
license_statusReport this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL.Reads text others writeNo findings
Why it is in this group
- The name "license_status" says "status": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Description, as the server wrote it Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.
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 write1
- 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.
Looked at Nov 20, 2026, 19:35 UTC, unchanged since Nov 13, 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
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/service-agreement
- Authorization servers
- https://mcp.zovo.one
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.zovo.one/mcp/service-agreement: tools/list returned 9 tools to an anonymous client, including agreement_create (write), agreement_update_status (write), clause_library (write), agreement_render (write), agreement_checklist (write) and 1 more
Posture changes
- Nov 13, 2026
- HTTP status of an anonymous initialize: 429 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 6
- Protocol version: none to 2025-06-18
- Nov 6, 2026
- RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource to https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/service-agreement
- Oct 29, 2026
- HTTP status of an anonymous initialize: 200 to 429
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 6 to 0
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
- Warnclause_library
The server marks "clause_library" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "list": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 429 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 6 (and 1 more).View diff
- HTTP status of an anonymous initialize: 429 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 6
- Protocol version: none to 2025-06-18
PostureRemote posture changed. RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource -> https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/service-agreement.View diff
- RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource to https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/service-agreement
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 429; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 6 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 429
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 6 to 0
- Protocol version: 2025-06-18 to none
Install
Pinned to version 0.23.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http service-agreement https://mcp.zovo.one/mcp/service-agreementclaude mcp add --transport http service-agreement https://mcp.zovo.one/mcp/service-agreementRun 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.
{
"permissions": {
"allow": [
"mcp__service-agreement__agreement_get",
"mcp__service-agreement__agreement_list",
"mcp__service-agreement__license_status"
],
"ask": [
"mcp__service-agreement__agreement_create",
"mcp__service-agreement__agreement_update_status",
"mcp__service-agreement__clause_library",
"mcp__service-agreement__agreement_render",
"mcp__service-agreement__agreement_checklist",
"mcp__service-agreement__license_activate"
],
"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 service-agreement. Review it before you use it.
Capability tags behind 1 rule
- mcp__service-agreement__license_status 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.theluckystrike/service-agreement/verify?hash=7e0f0f473e74a69c2f4a4f04124f20c51ae5e20179d9df79947a6f6330dbfca7" | jq -e '.changed == false'Pinned hash 7e0f0f473e74, from Nov 15, 2026, 05: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.theluckystrike/service-agreement/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.theluckystrike/service-agreement)Source: MCP Registry · repository. Synced Nov 2, 2026, 03:18 UTC.
McpStamp Service Agreement MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the McpStamp Service Agreement MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, 6 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the McpStamp Service Agreement MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the McpStamp Service Agreement 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 McpStamp Service Agreement MCP server have?
- 9 tools: 6 write, 3 read. agreement_create, agreement_update_status, clause_library, agreement_render, agreement_checklist, license_activate, agreement_get, agreement_list and 1 more.
Does the McpStamp Service Agreement MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the McpStamp Service Agreement MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the McpStamp Service Agreement MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.