Skip to content

GVRN Incorporation MCP server

ai.gvrn/incorporationgvrn.aistreamable-httpv1.0.1Scanned

Collect and submit company incorporation requests for review by GVRN's corpsec team.

7 tools: 1 can delete or cancel things, 1 do something that can't be undone, 3 change things and 2 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 1 does something that can't be undone. 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 GVRN Incorporation MCP server can do

The GVRN Incorporation MCP server is published by gvrn.ai, a domain the MCP Registry verified. It has 7 tools. It can delete or cancel things (1 tool: submit_incorporation), do things that cannot be undone, such as sending, paying or publishing (request_email_otp) and create or change data (3 tools: verify_email_otp, create_incorporation_draft and update_incorporation_draft). 2 tools only read.

1 tool reads private data (get_incorporation_guide); 3 tools bring in text other people can write (get_incorporation_guide, request_email_otp and get_incorporation_status); 1 tool can send data out of your system (request_email_otp). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

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 2 times since Anlyon Radar first saw them.

Last scanned Nov 11, 2026, version 1.0.1.

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.

7 tools

Deletes or cancels 1Claude Code: deny
  • submit_incorporationSubmits a draft for review by the GVRN team and returns the request status.No findings

    Why it is in this group

    • The name "submit_incorporation" says "submit": a word for a change.
    • The description says "Irreversible".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Submits a draft for review by the GVRN team and returns the request status. Requires a verificationToken for the email that created the draft, which becomes the contact for the request. Optional fields may be left blank. Irreversible: the draft becomes read-only and a review request is filed with the GVRN team.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
Can't be undone 1Claude Code: ask
  • request_email_otpSends a 6-digit verification code to the given email address.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "request_email_otp" says "request": a word for a change.
    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "request_email_otp" says "request" and "email": it writes something other people read.
    Description, as the server wrote it
    Sends a 6-digit verification code to the given email address. The code is exchanged for a verificationToken via verify_email_otp, and that token authorizes the draft tools. Codes expire after 10 minutes and are rate-limited per email.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 3Claude Code: ask
  • create_incorporation_draftCreates a new incorporation request draft bound to the verified email, using any fields provided.No findings

    Why it is in this group

    • The name "create_incorporation_draft" says "create": a word for a change.
    Description, as the server wrote it
    Creates a new incorporation request draft bound to the verified email, using any fields provided. Requires a verificationToken from verify_email_otp; every other field is optional. Returns a draftId that identifies the draft for later updates, submission, and status checks.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • update_incorporation_draftAdds or corrects fields on an existing draft (patch semantics: only provided fields are changed; array fields are replaced whole).No findings

    Why it is in this group

    • The name "update_incorporation_draft" says "update": a word for a change.
    Description, as the server wrote it
    Adds or corrects fields on an existing draft (patch semantics: only provided fields are changed; array fields are replaced whole). Requires a verificationToken for the email that created the draft. Fails once the draft has been submitted.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • verify_email_otpVerifies a 6-digit email code and returns a verificationToken valid for ~30 minutes.No findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    Verifies a 6-digit email code and returns a verificationToken valid for ~30 minutes. The draft tools require this token. Re-verifying the same email issues a fresh token that still reaches the same drafts.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • get_incorporation_guideReturns the full GVRN incorporation workflow guide: the fields collected, the email-verification steps, and the review lifecycle.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_incorporation_guide" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "return" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Returns the full GVRN incorporation workflow guide: the fields collected, the email-verification steps, and the review lifecycle. Also available as the MCP resource gvrn://incorporation/guide.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_incorporation_statusReturns the current status of an incorporation request (DRAFT → QUEUED_FOR_REVIEW → UNDER_REVIEW → COMPLETED).Reads text others writeNo findings

    Why it is in this group

    • The name "get_incorporation_status" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "review": it reads comments, which other people can write.
    Description, as the server wrote it
    Returns the current status of an incorporation request (DRAFT → QUEUED_FOR_REVIEW → UNDER_REVIEW → COMPLETED). Requires a verificationToken for the email that created the draft; requests are only visible to that email.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • 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.

3 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__incorporation__request_email_otp"
    ]
  }
}

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, 18:26 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
  • HighThe whole server

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

    Matched text

    https://incorporation-mcp.gvrn.ai: tools/list returned 7 tools to an anonymous client, including submit_incorporation (destructive), request_email_otp (irreversible), verify_email_otp (write), create_incorporation_draft (write), update_incorporation_draft (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. Tools4 changed.~4 changedView diff
  2. Tools6 changed.~6 changedView diff

Install

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

claude mcp add --transport http incorporation https://incorporation-mcp.gvrn.ai
claude mcp add --transport http incorporation https://incorporation-mcp.gvrn.ai

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__incorporation__get_incorporation_guide",
      "mcp__incorporation__get_incorporation_status"
    ],
    "ask": [
      "mcp__incorporation__request_email_otp",
      "mcp__incorporation__verify_email_otp",
      "mcp__incorporation__create_incorporation_draft",
      "mcp__incorporation__update_incorporation_draft"
    ],
    "deny": [
      "mcp__incorporation__submit_incorporation"
    ]
  }
}

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 incorporation. Review it before you use it.

Capability tags behind 3 rules
  • mcp__incorporation__get_incorporation_guide private-data, untrusted-input
  • mcp__incorporation__request_email_otp untrusted-input, outbound
  • mcp__incorporation__get_incorporation_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/ai.gvrn/incorporation/verify?hash=4c0864e49b4f0e300fc12fcf9ccf53245d46d8cd134916705f0c09bf9b2be561" | jq -e '.changed == false'

Pinned hash 4c0864e49b4f, from Nov 11, 2026, 19:17 UTC.

Watch

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

https://radar.anlyon.com/servers/ai.gvrn/incorporation/changes.xml

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

Badge

Anlyon Radar badge for ai.gvrn/incorporation
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.gvrn/incorporation.svg)](https://radar.anlyon.com/servers/ai.gvrn/incorporation)

Source: MCP Registry. Synced Oct 21, 2026, 17:41 UTC.

GVRN Incorporation MCP server: questions and answers

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

Is the GVRN Incorporation MCP server safe?

No scan can promise that. What its definitions show: 7 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 GVRN Incorporation MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: submit_incorporation.

Can the GVRN Incorporation MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: request_email_otp.

What tools does the GVRN Incorporation MCP server have?

7 tools: 1 destructive, 1 irreversible, 3 write, 2 read. submit_incorporation, request_email_otp, verify_email_otp, create_incorporation_draft, update_incorporation_draft, get_incorporation_guide and get_incorporation_status.

Does the GVRN Incorporation MCP server need sign-in or OAuth?

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

Does the GVRN Incorporation MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): request_email_otp.

Has the GVRN Incorporation MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.