Skip to content

MCP servers › io.github.Pankaj-bit361 › volanea

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.Pankaj-bit361/volanea

Email infrastructure on Volanea: build templates, segments and workflows, send and check email. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-10-23Topic: communication-and-social · AI-classifiedversion 1.0.2streamable HTTP27 tools

Summary

io.github.Pankaj-bit361/volanea is a remote MCP server listed in the official MCP registry at version 1.0.2. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 27 tools, 0 resources and 0 prompts.

Record checks

4 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Sign-in
none needed to open a session
Repository
public
Tools
27
Described as changing data
15 of 27 toolsAI-classified
Mainly works on
email, chat or social accountsAI-classified
Topic
communication-and-socialAI-classified
Last tested
2026-10-23

Add to your client

Observed fact

This server accepted a session without any credential and lists 11 tools whose name or declaration suggests they change data (volanea_create_template, volanea_create_segment, volanea_create_workflow, volanea_update_workflow, volanea_send_test_email and 6 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-23.

Worth knowing before you connect it

  • 15 tools are described as changing something (volanea_setup_domain, volanea_create_template, volanea_create_segment, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-23
Mode
read-only (no tool calls)
Latest version
1.0.2, published 2026-10-17 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-17 (earliest version still in the registry; older removed versions would be earlier)
Version history
3 versions listed, all on 2026-10-17; 3 in the 90 days before the 2026-10-23 snapshot.
Most recent 3 versions
  • 1.0.2 · 2026-10-17
  • 1.0.1 · 2026-10-17
  • 1.0.0 · 2026-10-17
(versions still listed in the registry only)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-23
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.0.2 (published 2026-10-17).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory
27tools
0resources
0prompts

What it mainly works on, as our AI model read its tool descriptions: email, chat or social accounts.

15 of 27 tools are described as changing something (creating, editing, deleting, sending or running). For 1 the reading was uncertain, so no mark is shown.

  • volanea_get_project_statusreads or searches

    “Call this FIRST in any integration session.”

    Publisher declares: read-only yes

    Takes no inputs.

  • volanea_get_api_referencereads or searches

    “Authoritative REST API reference for writing integration code into the user's app.”

    Publisher declares: read-only yes

    3 inputs, 1 required
    • resourcestringrequired“Which API resource to fetch reference docs for.”
    • indexOnlyboolean“Return just the operation list (operationId, method, path, summary) with no request/response schemas — the cheapest way to find the operationIds to pass in `op…”
    • operationsarray“operationIds to expand in full, e.g.”
  • volanea_list_resourcesreads or searches

    “List existing resources of one kind — use to find ids and avoid duplicating work.”

    Publisher declares: read-only yes

    1 input, 1 required
    • resourcestringrequired“Which resource to list.”
  • volanea_setup_domaincreates or changes datadescribed as changing data

    “Add a sending domain and/or check its DNS.”

    Publisher declares: idempotent yes · open-world yes

    1 input, 1 required
    • domainstringrequired“Domain name, e.g.”
  • volanea_get_templatereads or searches

    “Read ONE template in full — subject, HTML body, fromEmail, type, version, and the {{variables}} it expects.”

    Publisher declares: read-only yes

    1 input, 1 required
    • templateIdstringrequired“The `tmpl-…` id, exactly as returned by volanea_create_template or volanea_list_resources { templates }.”
  • volanea_render_templatecalculates or converts

    “Render a template with sample variables and return the resulting subject and HTML, plus any {{placeholders}} that went unsubstituted — WITHOUT sending anything or writing a row to the send log.”

    Publisher declares: read-only yes

    2 inputs, 1 required
    • templateIdstringrequired“The tmpl-...”
    • variablesobject“Sample values for {{variable}} placeholders.”
  • volanea_create_templatecreates or changes datadescribed as changing data

    “Create a reusable email template with {{variable}} placeholders.”

    Publisher declares: idempotent yes

    7 inputs, 4 required
    • namestringrequired“Template name, e.g.”
    • typestring“Decides who can receive it, so getting this wrong is a compliance problem rather than a cosmetic one.”
    • subjectstringrequired“Subject line.”
    • bodystringrequired“HTML body.”
    • previewTextstring“Inbox preview line (~100 chars visible).”
    • fromEmailstringrequired“Sender address — must be on a verified domain to deliver in live mode.”
    • fromNamestring“Human-readable sender name.”
  • volanea_create_segmentcreates or changes datadescribed as changing data

    “Create a dynamic audience segment from a condition tree (membership recomputes automatically).”

    Publisher declares: idempotent yes

    4 inputs, 1 required
    • namestring“Segment name.”
    • descriptionstring“Optional note for whoever reads the segment list later — why this audience exists, not what the filter does.”
    • conditionsobjectrequired“Condition tree over contacts.”
    • dryRunboolean“When true, only preview the match count and sample — nothing is created or modified.”
  • volanea_get_workflowreads or searches

    “Read ONE workflow in full — the complete node/edge graph with every node's config and canvas position, plus per-node run counts.”

    Publisher declares: read-only yes

    1 input, 1 required
    • workflowIdstringrequired“The wf-… id.”
  • volanea_create_workflowcreates or changes datadescribed as changing data

    “Create an event-triggered automation workflow from a node/edge graph.”

    Publisher declares: idempotent yes

    4 inputs, 3 required
    • namestringrequired“Workflow name.”
    • triggerstringrequired“e.g.”
    • graphobjectrequired“Automation graph.”
    • reentrystring“Whether a contact can re-enter: never, after finishing a previous walk (default), or always.”
  • volanea_update_workflowcreates or changes datadescribed as changing data

    “Update a workflow by id — edit the graph/trigger, or set status to 'active' (start processing live events) or 'paused'.”

    Publisher declares: idempotent yes

    6 inputs, 1 required
    • workflowIdstringrequired“The wf-… id.”
    • namestring“New display name.”
    • triggerstring“Event name that enrols a contact, e.g.”
    • graphobject“Automation graph.”
    • reentrystring“Whether a contact can enter again.”
    • statusstring“`draft` and `paused` workflows enrol NO ONE: matching events are silently ignored, which is the usual reason a workflow "does not fire".”
  • volanea_test_workflowruns code or commandsdescribed as changing data

    “END-TO-END TEST for an automation.”

    Publisher declares: open-world yes

    3 inputs, 2 required
    • workflowIdstringrequired“The wf-… id.”
    • emailstringrequired“Contact to enrol.”
    • waitMsnumber“How long to wait for steps to run before reading the log (default 750, max 5000).”
Show 15 more tools
  • volanea_track_eventruns code or commandsdescribed as changing data

    “Send a product event exactly as the user's app would (POST /v1/events).”

    Publisher declares: open-world yes

    3 inputs, 2 required
    • namestringrequired“Event name, e.g.”
    • emailstringrequired“Contact's email address.”
    • dataobject“Event payload; available to workflows as {{variables}}.”
  • volanea_check_recipientreads or searches

    “Answer "can I actually send to this address?" before writing or debugging a send path.”

    Publisher declares: read-only yes

    1 input, 1 required
    • emailstringrequired“Recipient address to check.”
  • volanea_send_test_emailsends messagesdescribed as changing data

    “Render and send a test message — either a saved template (`templateId` + sample `variables`) or ad-hoc `subject`/`html`.”

    Publisher declares: open-world yes

    6 inputs, 1 required
    • tostringrequired“Recipient address for the test.”
    • templateIdstring“Send a saved template.”
    • subjectstring“Ad-hoc subject.”
    • htmlstring“Ad-hoc HTML body.”
    • variablesobject“Sample values for {{variable}} placeholders.”
    • fromstring“Sender address.”
  • volanea_check_deliveryreads or searches

    “Inspect the send log to verify what actually happened.”

    Publisher declares: read-only yes

    5 inputs
    • emailIdstring“A specific email-… id for full detail including the rendered body.”
    • tostring“Filter the list by recipient address.”
    • statusstring“Filter by delivery state.”
    • sourcestring“Narrow the log to one origin: a direct API send, a campaign blast, a workflow step, or mail received at an inbound address.”
    • limitnumber“Max rows when listing (default 10, max 50).”
  • volanea_create_webhook_endpointcreates or changes datadescribed as changing data

    “Register an endpoint in the user's app to receive Volanea events, and get back its `whsec_…` SIGNING SECRET — you need that secret to write the signature-verification code into their codebase (see vo…”

    Publisher declares: idempotent yes

    3 inputs, 1 required
    • urlstringrequired“HTTPS endpoint in the user's app, e.g.”
    • descriptionstring“Optional label for the dashboard's endpoint list — e.g.”
    • eventsarray“Event patterns to subscribe to, e.g.”
  • volanea_test_webhook_deliveryruns code or commandsdescribed as changing data

    “Send a REAL signed test delivery to a registered endpoint and return what the endpoint answered — status code, response body, and the exact X-Volanea-Signature header sent.”

    Publisher declares: open-world yes

    2 inputs, 1 required
    • endpointIdstringrequired“The whep-...”
    • eventNamestring“Event name to simulate, e.g.”
  • volanea_create_campaign_draftcreates or changes datadescribed as changing data

    “Create a campaign as a DRAFT for the user to review and send from the dashboard.”

    12 inputs, 4 required
    • namestringrequired“Internal name for the campaign list — never shown to recipients.”
    • subjectstringrequired“Subject line recipients see.”
    • previewTextstring“The preview snippet most clients show beside the subject.”
    • bodystringrequired“HTML body.”
    • fromEmailstringrequired“Sender address.”
    • fromNamestring“Display name shown beside the from address, e.g.”
    • replyTostring“Where replies go, if not the from address.”
    • audiencestring“Who receives it.”
    • segmentIdstring“Required when audience = 'segment'.”
    • filterobject“Required when audience = 'filter'.”
    • abSubjectBstring“Variant-B subject line for an A/B test.”
    • abSamplePctnumber“Percent of the audience in the A/B sample (5–50).”
  • volanea_create_inboxcreates or changes datadescribed as changing data

    “Create an email inbox an agent can receive mail at (private beta — answers `inboxes_not_enabled` if the project isn't in it).”

    Publisher declares: idempotent yes

    4 inputs
    • clientIdstring“Idempotency key.”
    • usernamestring“Local part of the address.”
    • domainstring“A verified domain of the project whose MX points at SES (use a subdomain like agents.company.com).”
    • displayNamestring“From name on mail sent from this inbox.”
  • volanea_read_inboxreads or searches

    “Read an inbox.”

    Publisher declares: read-only yes

    3 inputs, 1 required
    • inboxIdstringrequired
    • threadIdstring“Open one thread.”
    • cursorstring“`nextCursor` from a previous thread list.”
  • volanea_wait_for_emailreads or searches

    “Wait (up to 55 s) for an email to arrive in an inbox and return it in full — the way to pick up a verification code, magic link, or reply.”

    Publisher declares: read-only yes

    5 inputs, 1 required
    • inboxIdstringrequired
    • afterstring“An emailId or ISO 8601 time.”
    • timeoutSecondsinteger
    • fromstring“Only mail from this address (or containing this text, e.g.”
    • subjectContainsstring“Only mail whose subject contains this text (case-insensitive).”
  • volanea_search_inboxreads or searches

    “Full-text search one inbox's mail — subject, sender, and reply text — best match first.”

    Publisher declares: read-only yes

    3 inputs, 2 required
    • inboxIdstringrequired
    • qstringrequired“Words to find; wrap a phrase in double quotes to match it exactly.”
    • limitinteger
  • volanea_cleanup_test_datadeletesdescribed as changing data

    “Remove the test artifacts YOU created in this project — the templates, segments, workflows, webhook endpoints, and campaign drafts made through this MCP server, plus any contacts it auto-created whil…”

    Publisher declares: destructive yes

    2 inputs
    • confirmboolean“Must be true to delete.”
    • kindsarray“Restrict cleanup to these kinds.”
  • volanea_update_webhook_endpointcreates or changes datadescribed as changing data

    “Change an existing webhook endpoint — flip `enabled`, repoint `url` after a tunnel restarts, or change which events it subscribes to.”

    Publisher declares: idempotent yes

    5 inputs, 1 required
    • endpointIdstringrequired“The `whep-…` id, from volanea_list_resources { webhooks }.”
    • urlstring“New HTTPS destination.”
    • enabledboolean“False stops deliveries without deleting the endpoint or rotating its secret.”
    • eventsarray“Replaces the subscribed event list entirely — send the full set, not a delta.”
    • descriptionstring“Label shown in the dashboard's endpoint list.”
  • volanea_delete_resourcedeletesdescribed as changing data

    “Permanently delete ONE resource by id.”

    Publisher declares: destructive yes

    3 inputs, 2 required
    • resourcestringrequired“Which kind of resource `id` refers to.”
    • idstringrequired“The resource id, e.g.”
    • confirmboolean“Must be true to actually delete.”
  • volanea_report_missing_tool

    “Report that this server lacks a tool you needed, so the gap gets closed instead of silently worked around.”

    Publisher declares: read-only yes

    2 inputs, 1 required
    • capabilitystringrequired“The missing capability in one line, phrased as the operation you wanted — e.g.”
    • contextstring“What you were building and what you did instead.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does
100% of 27 tools
Says what it returns
73% of 26 tools
States limits, defaults or errors
17% of 24 tools
Says when to use it
100% of 16 tools
Items covered per tool
2.8 of 4 on average

Counted from the listing

Parameters with a description
95% of 92
Tools with a description
100% of 27
Typical description length
479 characters

The tool set

Counted from the listing

Tools
27
Size of the list
about 14,984 tokens for an agent to load (characters ÷ 4)
Naming
27 of 27 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 27 of 27 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://api.volanea.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "volanea": {
      "url": "https://api.volanea.com/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "volanea": {
      "type": "http",
      "url": "https://api.volanea.com/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"volanea","type":"http","url":"https://api.volanea.com/mcp"}'
Claude Code
claude mcp add --transport http volanea https://api.volanea.com/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://api.volanea.com/mcp --transport http
  • Optional settings the entry also lists (left out above): Authorization.
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint api.volanea.com/mcpSession openedmatchesour test · 2026-10-23
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-23
Repository github.com/Pankaj-bit361/volanea-mcpOpens publiclymatchesapi.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.Pankaj-bit361 · 4 servers
GitHub owner
a personal account (Pankaj-bit361)
Repository
github.com/Pankaj-bit361/volanea-mcp
Stars
0
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.Pankaj-bit361/volanea

Answered from the data above

Is io.github.Pankaj-bit361/volanea safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. 15 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.github.Pankaj-bit361/volanea need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.Pankaj-bit361/volanea been security tested?

Partly. 3 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

What can io.github.Pankaj-bit361/volanea do?

It lists 27 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, delete, send messages, run code or commands and calculate or convert. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.Pankaj-bit361/volanea change or delete data?

15 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.Pankaj-bit361/volanea publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of io.github.Pankaj-bit361/volanea?

In github.com/Pankaj-bit361/volanea-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

Active servers whose topic is also “communication-and-social” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

3 exercised12 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 3
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 526 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 27 tools, 0 resources, 0 prompts.
  4. 1,688 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
AI-classified · 2026-10-23
Pricing modelAI-classified
no value
No value: the AI answer was held back because the quoted text did not clearly support it.
Programming language
not stated
GitHub detects no source language in this repository (docs-only or empty)
Hosting type
registry · 2026-10-23
MCP capability
tools
our test · 2026-10-23
Transport
streamable HTTP
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: a personal account · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-10-23
Maintenance
api.github.com · 2026-10-23
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.Pankaj-bit361/volanea: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.Pankaj-bit361/volanea

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.Pankaj-bit361/volanea)](https://protocolprobe.com/mcp/servers/io.github.Pankaj-bit361/volanea)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology