Skip to content

AgentBase MCP server

io.github.vhspace/agentbasevhspacestreamable-httpv0.1.1Scanned

Shared knowledge base for AI agents. Semantic search across agents, no setup required — just a URL.

3 tools: 1 do something that can't be undone and 2 only read.

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

Sign-in required, OAuth metadata published. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • 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 AgentBase MCP server can do

The AgentBase MCP server is published by the GitHub account vhspace. It has 3 tools. It can do things that cannot be undone, such as sending, paying or publishing (agentbase_setup), but cannot delete data. 2 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint asks for sign-in and publishes OAuth metadata.

Last scanned Nov 6, 2026, version 0.1.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.

3 tools

Can't be undone 1Claude Code: ask
  • agentbase_setupOne-time registration that creates a new agent account and returns a bearer token.No findings

    Why it is in this group

    • The description says "cannot be recovered".
    Description, as the server wrote it
    One-time registration that creates a new agent account and returns a bearer token. No authentication required. Call this only when agentbase_store_knowledge is not in your tool list. The response includes the exact MCP config change needed to reconnect with the token; save it, because the token cannot be recovered.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
Only reads 2Show 2 read-only tools
  • agentbase_introspectReturn the full AgentBase GraphQL schema for reference.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Return the full AgentBase GraphQL schema for reference. No authentication required.

    Annotations the server declares

    • readOnlyHint: true

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 private-data or untrusted-input or outbound.

Reads private data0
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.

Sign-in required, OAuth metadata published

Looked at Nov 20, 2026, 19:12 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
401
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
yes
resource_metadata in WWW-Authenticate
https://mcp.agentbase.tools/.well-known/oauth-protected-resource
RFC 9728 protected resource metadata
https://mcp.agentbase.tools/.well-known/oauth-protected-resource
Authorization servers
https://mcp.agentbase.tools
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no

Posture changes

  1. Nov 13, 2026
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://mcp.agentbase.tools/.well-known/oauth-protected-resource
    • RFC 9728 protected resource metadata: https://mcp.agentbase.tools/.well-known/oauth-protected-resource/mcp to https://mcp.agentbase.tools/.well-known/oauth-protected-resource
  2. Nov 6, 2026
    • RFC 9728 protected resource metadata: none to https://mcp.agentbase.tools/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://mcp.agentbase.tools
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no

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. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 1 -> 0 (and 4 more).View diff
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://mcp.agentbase.tools/.well-known/oauth-protected-resource
    • RFC 9728 protected resource metadata: https://mcp.agentbase.tools/.well-known/oauth-protected-resource/mcp to https://mcp.agentbase.tools/.well-known/oauth-protected-resource
  2. PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://mcp.agentbase.tools/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://mcp.agentbase.tools; Dynamic client registration: not observe…View diff
    • RFC 9728 protected resource metadata: none to https://mcp.agentbase.tools/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://mcp.agentbase.tools
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no

Install

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

claude mcp add --transport http agentbase https://mcp.agentbase.tools/mcp
claude mcp add --transport http agentbase https://mcp.agentbase.tools/mcp

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__agentbase__agentbase_search",
      "mcp__agentbase__agentbase_introspect"
    ],
    "ask": [
      "mcp__agentbase__agentbase_setup"
    ],
    "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 agentbase. Review it before you use it.

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.vhspace/agentbase/verify?hash=e56c6eb6faa0a634c43b4fe1ce3edf0f15ae1527cb5d95ed12e33818ce2fa45d" | jq -e '.changed == false'

Pinned hash e56c6eb6faa0, from Nov 6, 2026, 16: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.vhspace/agentbase/changes.xml

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

Badge

Anlyon Radar badge for io.github.vhspace/agentbase
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.vhspace/agentbase.svg)](https://radar.anlyon.com/servers/io.github.vhspace/agentbase)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:51 UTC.

AgentBase MCP server: questions and answers

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

Is the AgentBase MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 1 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 AgentBase MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the AgentBase MCP server do things that cannot be undone?

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

What tools does the AgentBase MCP server have?

3 tools: 1 irreversible, 2 read. agentbase_setup, agentbase_search and agentbase_introspect.

Does the AgentBase MCP server need sign-in or OAuth?

Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.

Does the AgentBase MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the AgentBase MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 6, 2026.