Aura
REMOTE · AURA.ROHNELT.DEV · SCANNED SEP 24
Email address, webhook, durable memory and zero-token waiting for agents. Paid in USDC via x402.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 16 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1759 tokens (~109/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "credit_deposit" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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
claude mcp add --transport http dev-rohnelt-aura-aura 'https://aura.rohnelt.dev/mcp'
{
"mcpServers": {
"dev-rohnelt-aura-aura": {
"url": "https://aura.rohnelt.dev/mcp"
}
}
} {
"servers": {
"dev-rohnelt-aura-aura": {
"type": "http",
"url": "https://aura.rohnelt.dev/mcp"
}
}
} [mcp_servers.dev-rohnelt-aura-aura] url = "https://aura.rohnelt.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-rohnelt-aura-aura": {
"type": "remote",
"url": "https://aura.rohnelt.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-rohnelt-aura-aura --url 'https://aura.rohnelt.dev/mcp' --transport streamable-http
mcp_servers:
dev-rohnelt-aura-aura:
url: "https://aura.rohnelt.dev/mcp" {
"McpServers": {
"dev-rohnelt-aura-aura": {
"Transport": "http",
"Url": "https://aura.rohnelt.dev/mcp"
}
}
} assistant mcp add dev-rohnelt-aura-aura -t streamable-http -u 'https://aura.rohnelt.dev/mcp'
{
"mcpServers": {
"dev-rohnelt-aura-aura": {
"type": "http",
"url": "https://aura.rohnelt.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 23 Sept 26 0
- Stability: 0.97 → pass security
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
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 24 Sept 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=YE1,O=Let's Encrypt,C=US | 24 Aug 2026 | 22 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5722e6fecbcc271e6ffd085986073ba1ddd |
| SANs: aura.rohnelt.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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. | present | 60074 | 8 | Verified |
| rohnelt.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| 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 | Verified | 200 | |
| http (plaintext) | http://aura.rohnelt.dev/mcp | HTTPS enforced | 301 | https://aura.rohnelt.dev/mcp |
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 →
await Wait for something (burns zero tokens) ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| lookback_seconds | integer | – | 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 | – | yes | What to wait for. |
| timeout_seconds | integer | – | – |
No output schema declared.
No examples provided.
capabilities Describe Aura ~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 Top up balance ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | string | – | How much credit to buy. |
No output schema declared.
No examples provided.
hook_create Create a webhook URL ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| slug | string | yes | Path segment for the URL. Must be unique within your handle. |
No output schema declared.
No examples provided.
identity_create Claim an identity ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | Optional label shown on your public profile. |
| message | string | yes | The exact text you signed. Must contain your wallet address and an ISO-8601 timestamp no older than 10 minutes. |
| signature | string | yes | EIP-191 personal_sign of the message field, proving you control the wallet. |
| wallet | string | yes | Your EVM wallet address. This is your permanent identity. |
No output schema declared.
No examples provided.
inbox_list List received mail ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | – |
| limit | integer | – | – |
| unread_only | boolean | – | – |
No output schema declared.
No examples provided.
inbox_read Read a message ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
memory_delete Forget ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
No output schema declared.
No examples provided.
memory_get Recall by key ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
No output schema declared.
No examples provided.
memory_list List memory keys ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| prefix | string | – | – |
No output schema declared.
No examples provided.
memory_search Search memory ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| q | string | yes | Natural-language description of what you are looking for. |
| tag | string | – | – |
No output schema declared.
No examples provided.
memory_set Remember something ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | Stable identifier. Writing the same key overwrites it. |
| tags | array | – | – |
| ttl_seconds | integer | – | Auto-delete after this many seconds. |
| value | string | yes | The content to remember. |
No output schema declared.
No examples provided.
park Park state and exit ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| callback_url | string | – | If set, Aura POSTs the state and the event here when it fires. |
| expires_in_hours | integer | – | – |
| note | string | – | A reminder to your future self about what you were doing. |
| on | – | yes | What should wake you. |
| state | object | yes | Arbitrary JSON you want back later. Returned exactly as given. |
No output schema declared.
No examples provided.
resume Resume parked work ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| park_id | string | – | Claim one specific park. Omit to claim the oldest ready one. |
| wait_seconds | integer | – | Optionally block up to this long for a park to become ready. |
No output schema declared.
No examples provided.
signal Signal another agent ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Signal name the recipient can filter on. |
| payload | object | – | – |
| to | string | yes | Recipient Aura handle. |
No output schema declared.
No examples provided.
whoami Who am I ~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.
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 78 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?
No. We connected to Aura without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Aura MCP server still maintained?
Aura is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.