Pay-per-call MCP tools and signed on-chain attestations: 20 free/day, then x402 or a spend key.
- Remote endpoint
Uptime
Checked · every day
100%from 12 days of checks
Up without downtime on 11 of 11 days with data.
- No downtime
- Degraded
- Down over 5 minutes
- No data
- Not checked yet
Response time
Median 540 ms, slowest 5% 1552 ms for the handshake and the tool list, over 30 days.
How far each check got
- Reached the address 100%
- Completed the handshake 100%
- Listed its tools 100%
31 tools at the last answer; the list changed on 2 Nov.
Every day
| Day | Result | Checks | Median |
|---|---|---|---|
| 11 Nov (today) | No verdict yet | 0 | – |
| 10 Nov | No downtime | 1of 1 | 526 ms |
| 9 Nov | No downtime | 1of 1 | 526 ms |
| 8 Nov | No downtime | 1of 1 | 548 ms |
| 7 Nov | No downtime | 1of 1 | 519 ms |
| 6 Nov | No downtime | 1of 1 | 843 ms |
| 5 Nov | No downtime | 1of 1 | 907 ms |
| 4 Nov | No downtime | 1of 1 | 437 ms |
| 3 Nov | No downtime | 1of 1 | 585 ms |
| 2 Nov | No downtime | 1of 1 | 839 ms |
| 1 Nov | No downtime | 1of 1 | 911 ms |
| 31 Oct | No downtime | 2 | 915 ms |
A failure counts as down time only when a second check five minutes later fails too. How we check
Connect to the publisher's own endpoint
Paste into Settings › Connectors › Add custom connector:
https://mcp.naxytra.com/mcp Run in a terminal:
claude mcp add --transport http xytara-mcp-executor https://mcp.naxytra.com/mcp Add to ~/.cursor/mcp.json:
Add to ~/.config/devin/mcp_config.json:
Add to mcp.json (Program › Install › Edit mcp.json):
Add to config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows):
Add to ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project):
Add to ~/.config/eca/config.json (global) or .eca/config.json in the project:
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
{
"mcpServers": {
"xytara-mcp-executor": {
"url": "https://mcp.naxytra.com/mcp"
}
}
} Add to .vscode/mcp.json:
{
"servers": {
"xytara-mcp-executor": {
"type": "http",
"url": "https://mcp.naxytra.com/mcp"
}
}
} Add to ~/.config/zed/settings.json:
{
"context_servers": {
"xytara-mcp-executor": {
"url": "https://mcp.naxytra.com/mcp"
}
}
} Add to cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):
{
"mcpServers": {
"xytara-mcp-executor": {
"type": "streamableHttp",
"url": "https://mcp.naxytra.com/mcp"
}
}
} Add to ~/.continue/config.yaml:
mcpServers:
- name: "xytara-mcp-executor"
type: streamable-http
url: "https://mcp.naxytra.com/mcp" Add to ~/.config/goose/config.yaml:
extensions:
"xytara-mcp-executor":
type: streamable_http
name: "xytara-mcp-executor"
enabled: true
uri: "https://mcp.naxytra.com/mcp"
headers: {}
env_keys: []
envs: {}
timeout: 300 Add to ~/.gemini/settings.json:
{
"mcpServers": {
"xytara-mcp-executor": {
"httpUrl": "https://mcp.naxytra.com/mcp"
}
}
} Run in a terminal:
codex mcp add xytara-mcp-executor --url https://mcp.naxytra.com/mcp Add to ~/.llm/config.json:
Add to resources/assets/config/mcp.json in the installed app:
Add to ~/.boltai/mcp.json:
{
"mcpServers": {
"xytara-mcp-executor": {
"url": "https://mcp.naxytra.com/mcp"
}
}
} This server's endpoint speaks streamable HTTP, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/agenvoy/mcp.json:
{
"servers": {
"xytara-mcp-executor": {
"url": "https://mcp.naxytra.com/mcp"
}
}
} Add to ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
{
"amp.mcpServers": {
"xytara-mcp-executor": {
"url": "https://mcp.naxytra.com/mcp"
}
}
} Add to anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:
{
"mcpServers": {
"xytara-mcp-executor": {
"type": "streamable",
"url": "https://mcp.naxytra.com/mcp"
}
}
} Add to Augment Settings Panel – MCP section – Import from JSON (VS Code extension):
{
"mcpServers": {
"xytara-mcp-executor": {
"type": "http",
"url": "https://mcp.naxytra.com/mcp"
}
}
} For agents: the install prompt
Every step above as one Markdown text, for an assistant installing it for you.
# Install the MCP server xytara MCP Executor (`com.naxytra/xytara-mcp-executor`)
Its page: https://plug.directory/servers/com.naxytra/xytara-mcp-executor
It runs on the publisher's servers; the client connects to its URL.
Use the section for the person's client.
## Claude Desktop
Paste into Settings › Connectors › Add custom connector:
```text
https://mcp.naxytra.com/mcp
```
## Claude Code
Run in a terminal:
```sh
claude mcp add --transport http xytara-mcp-executor https://mcp.naxytra.com/mcp
```
## Cursor, Devin Desktop, LM Studio, oterm, Bob Shell, ECA, Kiro, Kiro CLI
Merge into the place for the person's client:
- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- Bob Shell: ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
- Kiro: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)
- Kiro CLI: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)
```json
{
"mcpServers": {
"xytara-mcp-executor": {
"url": "https://mcp.naxytra.com/mcp"
}
}
}
```
## VS Code
Merge into .vscode/mcp.json:
```json
{
"servers": {
"xytara-mcp-executor": {
"type": "http",
"url": "https://mcp.naxytra.com/mcp"
}
}
}
```
## Zed
Merge into ~/.config/zed/settings.json:
```json
{
"context_servers": {
"xytara-mcp-executor": {
"url": "https://mcp.naxytra.com/mcp"
}
}
}
```
## Cline
Merge into cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):
```json
{
"mcpServers": {
"xytara-mcp-executor": {
"type": "streamableHttp",
"url": "https://mcp.naxytra.com/mcp"
}
}
}
```
## Continue
Merge into ~/.continue/config.yaml:
```yaml
mcpServers:
- name: "xytara-mcp-executor"
type: streamable-http
url: "https://mcp.naxytra.com/mcp"
```
## Goose
Merge into ~/.config/goose/config.yaml:
```yaml
extensions:
"xytara-mcp-executor":
type: streamable_http
name: "xytara-mcp-executor"
enabled: true
uri: "https://mcp.naxytra.com/mcp"
headers: {}
env_keys: []
envs: {}
timeout: 300
```
## Gemini CLI
Merge into ~/.gemini/settings.json:
```json
{
"mcpServers": {
"xytara-mcp-executor": {
"httpUrl": "https://mcp.naxytra.com/mcp"
}
}
}
```
## Codex
Run in a terminal:
```sh
codex mcp add xytara-mcp-executor --url https://mcp.naxytra.com/mcp
```
## mcp-client-cli, TUUI, BoltAI
This server's endpoint speaks streamable HTTP, which this client's documentation does not list among its transports; use another client for it.
## Agenvoy
Merge into ~/.config/agenvoy/mcp.json:
```json
{
"servers": {
"xytara-mcp-executor": {
"url": "https://mcp.naxytra.com/mcp"
}
}
}
```
## Amp
Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
```json
{
"amp.mcpServers": {
"xytara-mcp-executor": {
"url": "https://mcp.naxytra.com/mcp"
}
}
}
```
## AnythingLLM
Merge into anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:
```json
{
"mcpServers": {
"xytara-mcp-executor": {
"type": "streamable",
"url": "https://mcp.naxytra.com/mcp"
}
}
}
```
## Augment Code
Merge into Augment Settings Panel – MCP section – Import from JSON (VS Code extension):
```json
{
"mcpServers": {
"xytara-mcp-executor": {
"type": "http",
"url": "https://mcp.naxytra.com/mcp"
}
}
}
```
Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.
From the publisher's entry in the Official MCP Registry (the registry entry). Report a problem