generated: '2026-08-03'
method: probed
status: published
provider_published: true
source: https://amuncore.com/mcp
description: 'AmunCore is MCP-native by design: the REST endpoints a user builds over
  their own database become tools an AI assistant can call, under the same keys, permissions
  and audit trail. The MCP endpoint is live and token-gated — it answers JSON-RPC
  with a well-formed error rather than an HTML page, which is a good sign of a real
  implementation rather than a marketing route.'
verified: '2026-08-03'
server:
  name: amuncore
  transport: http
  url: https://amuncore.com/mcp
  auth: MCP-Token header
  deployment: vendor-hosted
evidence:
- url: https://amuncore.com/mcp
  status: 405
  method: GET
  note: exists; GET not allowed
- url: https://amuncore.com/mcp
  status: 401
  method: POST
  note: 'jsonrpc tools/list and initialize both returned {"jsonrpc":"2.0","error":{"code":-32001,"message":"Unauthorized:
    missing MCP-Token header"}} — a correct JSON-RPC error, so the server is real
    and simply requires a token.'
gaps:
- Tool list not enumerable without a token, so the exposed tools are whatever endpoints
  a given user has built — the surface is per-tenant by design rather than fixed.