Neura Relay MCP
com.neurarelayPublished by neurarelay.comOfficial publisherv0.1.0Updated Oct 27, 2026
Govern proposed Action Cards with Decision Receipts before developer-owned execution.
Overview
Remote MCP endpoint that lets an assistant govern proposed Action Cards with Decision Receipts before developer-owned execution.
- What you can do
- Govern proposed Action Cards: the server is built around reviewing proposed actions and issuing Decision Receipts before execution.
- Hand off execution: actual running of approved actions stays with the developer's own systems rather than the server.
- No tool list is published, so the exact operations available to an assistant are not documented in the supplied material.
- When to use it
- Consider it when you want an assistant to propose actions that are reviewed and recorded with Decision Receipts, while execution remains under developer control. It is aimed at teams that need an approval or governance step between an AI proposal and the code that carries it out.
- Requirements
- A remote streamable HTTP endpoint at the provider's site. OAuth authentication is required, supplied as a Bearer token in the Authorization header, obtained from a Relay Workspace sandbox or controlled production/private access. No local package or environment variables are declared.
Installation
In SourceWeft
- Open Neura Relay MCP in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.neurarelay%2Frelay-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"neura-relay": {
"type": "http",
"url": "https://www.neurarelay.com/mcp"
}
}
}Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.