Grisoco AI security audits

com.grisocoPublished by grisoco.comOfficial publisherv1.0.0Updated Oct 25, 2026

Smart-contract security audits for EVM chains and DAML: quote, run and fetch reports.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server from Grisoco that lets an assistant quote, run and retrieve smart-contract security audits for EVM chains and DAML.

What you can do
Quote, run and fetch smart-contract security audit reports for EVM chains and DAML, as described in the registry entry. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to start or check security audits of smart contracts on EVM chains or DAML within a Grisoco workspace, instead of handling the audit workflow by hand.
Requirements
A remote endpoint at grisoco.com over streamable HTTP. A Grisoco account and API key are required, sent as a bearer token in the Authorization header; the key is created in the workspace under Agent API. Network access is needed.
Before you install
The server requires a Grisoco API key in the Authorization header, so treat it as a secret and avoid exposing it in logs or shared configuration. Audits may consume paid quota or credits on your Grisoco account; confirm pricing before running them. Audit requests and contract details are sent to Grisoco's servers.

Installation

In SourceWeft

  1. Open Grisoco AI security audits in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.grisoco%2Faudits/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "grisoco-ai-security-audits": {
      "type": "http",
      "url": "https://grisoco.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 10, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.