Vara MCP — Field Intelligence Scan Server
io.github.kushkillerjsixx66/vara-mcp-serverkushkillerjsixx66streamable-httpv1.30.0Scanned
Governed external-environment scanning: signal harvest, Field Intel Reports, per-signal lineage.
6 tools: 2 change things and 4 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 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 Vara MCP — Field Intelligence Scan Server can do
The Vara MCP — Field Intelligence Scan Server is published by the GitHub account kushkillerjsixx66. It has 6 tools. It can create or change data (2 tools: vara_run_scan and vara_generate_fir), but cannot delete data. 4 tools only read.
1 tool reads private data (vara_query_signals).
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 once since Anlyon Radar first saw them.
Last scanned Nov 21, 2026, version 1.30.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.
6 tools
Changes things 2Claude Code: ask
vara_generate_firGenerate an Operator-Tier or lightweight Field Intel Report from a scan_id.No findings
Why it is in this group
- The name "vara_generate_fir" says "generate": a word for a change.
Description, as the server wrote it Generate an Operator-Tier or lightweight Field Intel Report from a scan_id.
Annotations the server declares
- read_only_hint: true
- destructive_hint: false
- idempotent_hint: true
- open_world_hint: false
vara_run_scanExecute a full Real Vara scan using the operational dual-track, multi-timescale pipeline.No findings
Why it is in this group
- The name "vara_run_scan" says "run": a word for a change.
Description, as the server wrote it Execute a full Real Vara scan using the operational dual-track, multi-timescale pipeline. This tool changes Vara runtime state.
Annotations the server declares
- read_only_hint: false
- destructive_hint: false
- idempotent_hint: false
- open_world_hint: true
Only reads 4Show 4 read-only tools
vara_get_scanRetrieve a complete historical VaraScanReport by scan_id or short prefix.No findings
Why it is in this group
- The name "vara_get_scan" says "get": a word for reading.
Description, as the server wrote it Retrieve a complete historical VaraScanReport by scan_id or short prefix.
Annotations the server declares
- read_only_hint: true
- destructive_hint: false
- idempotent_hint: true
- open_world_hint: false
vara_get_veil_stateInspect current Veil hold entries and trajectories.No findings
Why it is in this group
- The name "vara_get_veil_state" says "get": a word for reading.
Description, as the server wrote it Inspect current Veil hold entries and trajectories.
Annotations the server declares
- read_only_hint: true
- destructive_hint: false
- idempotent_hint: true
- open_world_hint: false
vara_list_scansList historical Vara scan metadata from the local archive.No findings
Why it is in this group
- The name "vara_list_scans" says "list": a word for reading.
Description, as the server wrote it List historical Vara scan metadata from the local archive.
Annotations the server declares
- read_only_hint: true
- destructive_hint: false
- idempotent_hint: true
- open_world_hint: false
vara_query_signalsQuery the committed Vault corpus and optionally the current Veil hold.Reads private dataNo findings
Why it is in this group
- The name "vara_query_signals" says "query": a word for reading.
What it can reach
- private-dataThe description's first sentence says "query" and "vault": it reads secrets.
Description, as the server wrote it Query the committed Vault corpus and optionally the current Veil hold.
Annotations the server declares
- read_only_hint: true
- destructive_hint: false
- idempotent_hint: true
- open_world_hint: 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 untrusted-input or outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- 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:07 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
- 2
- 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://vara-mcp-server.vercel.app/api/mcp: tools/list returned 6 tools to an anonymous client, including vara_run_scan (write), vara_generate_fir (write)
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.
Tools1 changed.~1 changedView diff
- Changed:vara_run_scanChanges thingsinputSchema
Install
Pinned to version 1.30.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http vara https://vara-mcp-server.vercel.app/api/mcpclaude mcp add --transport http vara https://vara-mcp-server.vercel.app/api/mcpRun 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__vara__vara_list_scans",
"mcp__vara__vara_get_scan",
"mcp__vara__vara_query_signals",
"mcp__vara__vara_get_veil_state"
],
"ask": [
"mcp__vara__vara_run_scan",
"mcp__vara__vara_generate_fir"
],
"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 vara. Review it before you use it.
Capability tags behind 1 rule
- mcp__vara__vara_query_signals private-data
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.kushkillerjsixx66/vara-mcp-server/verify?hash=8080c5d7a8d64851dd3a7bafcb97794f18678f3108c8720c6d0c5bcf64895a42" | jq -e '.changed == false'Pinned hash 8080c5d7a8d6, from Nov 21, 2026, 00:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.kushkillerjsixx66/vara-mcp-server/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.kushkillerjsixx66/vara-mcp-server)Source: MCP Registry. Synced Oct 21, 2026, 18:37 UTC.
Vara MCP — Field Intelligence Scan Server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Vara MCP — Field Intelligence Scan Server safe?
- No scan can promise that. What its definitions show: 6 tools, 2 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 Vara MCP — Field Intelligence Scan Server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Vara MCP — Field Intelligence Scan 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 Vara MCP — Field Intelligence Scan Server have?
- 6 tools: 2 write, 4 read. vara_run_scan, vara_generate_fir, vara_list_scans, vara_get_scan, vara_query_signals and vara_get_veil_state.
Does the Vara MCP — Field Intelligence Scan Server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Vara MCP — Field Intelligence Scan Server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Vara MCP — Field Intelligence Scan Server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 6, 2026. Every change is on this page and in its Atom feed.