Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Aura

REMOTE · AURA.ROHNELT.DEV

Email address, webhook, durable memory and zero-token waiting for agents. Paid in USDC via x402.

Available components

0 this week 25 Trust /100

Last scanned (19 hours ago)

Scores higher than 10% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Memory and Knowledge

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (5)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (6)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Oct 26 −53
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 0
    • Stability: 0.97 → pass security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 24 Aug 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://aura.rohnelt.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=aura.rohnelt.dev CN=YE2,O=Let's Encrypt,C=US 23 Oct 2026 21 Jan 2027 ECDSA 256 ECDSA-SHA384 64c91d2ed91670d64cb4737af59ad5c59aa
SANs: aura.rohnelt.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of aura.rohnelt.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
rohnelt.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 502
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff
referrer-policy no-referrer-when-downgrade

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://aura.rohnelt.dev/mcp HTTP error 502
http (plaintext) http://aura.rohnelt.dev/mcp HTTPS enforced 301 https://aura.rohnelt.dev/mcp
MCP tools · 16 exposed · ~1,626 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
await ~200

Block on an open HTTP connection until a trigger fires — an email arrives, a webhook is hit, another agent signals you, or a deadline passes. Returns the instant it happens. If nothing fires before the timeout, the call is refunded: you are only charged when something is actually delivered. When to use: Call INSTEAD of polling in a loop. A poll loop costs a full inference per iteration; waiting inside this single call costs you nothing beyond the flat fee. Use it for verification codes, callbacks and approvals that land within minutes. Price: US$0.004000 per call. This call blocks until it resolves; waiting inside it costs you no tokens.

NameTypeReqDescription
lookback_secondsinteger–Also match events that arrived this many seconds BEFORE the call. Covers the gap between submitting a form and starting to wait. Raise it if you were slow to call.
on–yesWhat to wait for.
timeout_secondsinteger––

No output schema declared.

No examples provided.

capabilities ~64

Return the full machine-readable manifest of Aura: every operation, its price in USD, its input schema and how to pay. Free. When to use: Call this first if you have never used Aura and want to know what it can do and what it costs. Price: Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

credit_deposit ~96

Pay USDC once and receive spendable Aura credit. Individual calls are far too cheap to settle on-chain one at a time, so you deposit once and Aura debits each call off-chain. When to use: Call when your balance is low, or when a paid call returns 402. A US$1 deposit covers hundreds of operations. Price: Free.

NameTypeReqDescription
amount_usdstring–How much credit to buy.

No output schema declared.

No examples provided.

hook_create ~94

Mint a public URL that anyone can POST to. Deliveries become events you can await on. When to use: Call when a third-party service offers a callback and you have nowhere to receive it — you are not a server, Aura is. Price: US$0.001000 per call.

NameTypeReqDescription
descriptionstring––
slugstringyesPath segment for the URL. Must be unique within your handle.

No output schema declared.

No examples provided.

identity_create ~174

Turn a wallet address into a permanent agent identity: a handle, a REAL email address that receives mail, a webhook URL, and an API token. Free, and grants a small trial credit. When to use: Call this once, before anything else. You need the returned token for every other call, and the email address is what lets you sign up for third-party services. Price: Free.

NameTypeReqDescription
labelstring–Optional label shown on your public profile.
messagestringyesThe exact text you signed. Must contain your wallet address and an ISO-8601 timestamp no older than 10 minutes.
signaturestringyesEIP-191 personal_sign of the message field, proving you control the wallet.
walletstringyesYour EVM wallet address. This is your permanent identity.

No output schema declared.

No examples provided.

inbox_list ~86

List messages delivered to your Aura email address, newest first. When to use: Call after signing up somewhere, to see what arrived. To block until mail lands, use await instead — it is far cheaper than polling this. Price: US$0.001000 per call.

NameTypeReqDescription
fromstring––
limitinteger––
unread_onlyboolean––

No output schema declared.

No examples provided.

inbox_read ~67

Return the full parsed body of one message, plus any verification code or confirmation link found in it. When to use: Call with an id from inbox.list when you need the full text or the link. Price: US$0.001000 per call.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

memory_delete ~50

Delete a stored key. Free — keeping your own state tidy should never cost you. When to use: Call when a stored fact is stale or wrong. Price: Free.

NameTypeReqDescription
keystringyes–

No output schema declared.

No examples provided.

memory_get ~58

Fetch one stored value by its exact key. When to use: Call when you know the key you wrote earlier. Cheaper and more precise than memory.search. Price: US$0.000500 per call.

NameTypeReqDescription
keystringyes–

No output schema declared.

No examples provided.

memory_list ~62

List your stored keys with metadata, without returning the values. When to use: Call to see what you already know before deciding what to fetch. Price: US$0.000500 per call.

NameTypeReqDescription
limitinteger––
prefixstring––

No output schema declared.

No examples provided.

memory_search ~79

Find stored memories by meaning rather than by exact key. When to use: Call when you remember roughly what you stored but not the key you used. Price: US$0.002000 per call.

NameTypeReqDescription
limitinteger––
qstringyesNatural-language description of what you are looking for.
tagstring––

No output schema declared.

No examples provided.

memory_set ~119

Store a durable key/value fact bound to your wallet. Survives your process dying. When to use: Call whenever you learn something a later run will need: a decision, where a credential lives, a user preference, progress through a long task. Price: US$0.000800 per call.

NameTypeReqDescription
keystringyesStable identifier. Writing the same key overwrites it.
tagsarray––
ttl_secondsinteger–Auto-delete after this many seconds.
valuestringyesThe content to remember.

No output schema declared.

No examples provided.

park ~176

Hand Aura your state plus a wake condition, then terminate. Aura holds the state, watches for the condition, and returns it byte-identical when you come back with resume. Optionally POSTs to a callback URL when it fires. When to use: Call when the wait outlasts your process — hours, days, or an approval that lands tomorrow. Cheaper and safer than staying alive. Price: US$0.005000 per call.

NameTypeReqDescription
callback_urlstring–If set, Aura POSTs the state and the event here when it fires.
expires_in_hoursinteger––
notestring–A reminder to your future self about what you were doing.
on–yesWhat should wake you.
stateobjectyesArbitrary JSON you want back later. Returned exactly as given.

No output schema declared.

No examples provided.

resume ~162

Claim state from a park whose trigger has fired. Returns the original state and the event that woke it. Free when nothing is ready, so calling it at the start of every run costs you nothing until it actually hands work back. When to use: Call at the START of every run. If a previous instance of you parked something and it fired, this hands the work back. If nothing is ready it tells you so, cheaply. Price: US$0.002000 per call. This call blocks until it resolves; waiting inside it costs you no tokens.

NameTypeReqDescription
park_idstring–Claim one specific park. Omit to claim the oldest ready one.
wait_secondsinteger–Optionally block up to this long for a park to become ready.

No output schema declared.

No examples provided.

signal ~87

Send a named JSON message to another Aura agent by handle. They can await on it. When to use: Call to hand work to, or coordinate with, another agent without shared infrastructure. Price: US$0.002000 per call.

NameTypeReqDescription
namestring–Signal name the recipient can filter on.
payloadobject––
tostringyesRecipient Aura handle.

No output schema declared.

No examples provided.

whoami ~52

Return your handle, email address, webhook base URL, current balance and quota usage. Free. When to use: Call when you need your own email address, or to check your balance before spending. Price: Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Aura MCP server?

Aura is a hosted endpoint at https://aura.rohnelt.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · aura.rohnelt.dev

# add to Claude Code
claude mcp add --transport http dev-rohnelt-aura-aura 'https://aura.rohnelt.dev/mcp'
Common questions

What is the Aura MCP server?

Aura is an MCP server listed in the public MCP registry as dev.rohnelt.aura/aura. Email address, webhook, durable memory and zero-token waiting for agents. Paid in USDC via x402. This page covers its hosted endpoint (https://aura.rohnelt.dev/mcp).

Is the Aura MCP server safe to use?

Aura scores 25 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Aura MCP server expose?

Aura exposes 16 tools: capabilities, identity_create, whoami, credit_deposit, memory_set, and 11 more. Their descriptions and schemas cost roughly 1,626 tokens of context every time the server is loaded.

Does the Aura MCP server require authentication?

Its publisher declares no required credentials for Aura. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Aura MCP server still maintained?

Aura is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Aura MCP server?

VerifyMCP ran 5 checks on Aura, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Aura: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.