Phishnoo Sandbox

nl.phishnoo.apiPublished by api.phishnoo.nlOfficial publisherv0.1.0Updated Nov 8, 2026

Explore synthetic security awareness metrics and file example threat reports.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

A remote Phishnoo sandbox server for exploring synthetic security awareness metrics and filing example threat reports.

What you can do
  • Explore synthetic security awareness metrics.
  • File example threat reports.
  • No tools are listed in the manifest, so the exact operations are not documented; the description only covers these two sandbox activities.
When to use it
Useful when you want to try Phishnoo's security awareness and threat reporting workflows against sample, non-production data before working with real data.
Requirements
A remote endpoint at api.phishnoo.nl over streamable HTTP. A bearer token in the Authorization header is required: an operator-issued Phishnoo sandbox key. No packages or environment variables are declared.
Before you install
The server requires a secret credential, the operator-issued sandbox key, sent in the Authorization header; keep it private and use only a sandbox key, not a production one. Filing reports may create or change data in the sandbox. The data is described as synthetic, so do not treat it as real security findings.

Installation

In SourceWeft

  1. Open Phishnoo Sandbox 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/nl.phishnoo.api%2Fsandbox/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": {
    "phishnoo-sandbox": {
      "type": "http",
      "url": "https://api.phishnoo.nl/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. v0.1.0LatestNov 8, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.