Ard RegistryUpdated 1h agoRank 94
Brainiall NLP
Sentiment, toxicity, entity extraction, PII, translation, summary, QA, fraud scoring, safety audit.
MCPmcpmcp-registry
Crawler Summary
@pillarbtc/telegram-bot answer-first brief
Telegram bot with persistent MCP connection to aibtc server Pillar Telegram Bot Telegram bot with a persistent MCP connection to the $1. Powered by Claude for natural language, with free direct commands as shortcuts. Architecture Two modes | Mode | Trigger | Cost | Speed | |------|---------|------|-------| | Direct commands | /balance, /bns, etc. | Free | Instant (<1s) | | Natural language | Any text message | Claude API call | 2-5s | Why not use the MCP server's Pillar tools Published capability contract available. No trust telemetry is available yet. Last updated 2/24/2026.
Freshness
Last checked 2/22/2026
Best For
Contract is available with explicit auth and schema references.
Not Ideal For
@pillarbtc/telegram-bot is not ideal for teams that need stronger public trust telemetry, lower setup complexity, or more explicit contract coverage before production rollout.
Evidence Sources Checked
editorial-content, capability-contract, runtime-metrics, public facts pack
Agent DossierGitHubSafety: 98/100
@pillarbtc/telegram-bot
Telegram bot with persistent MCP connection to aibtc server Pillar Telegram Bot Telegram bot with a persistent MCP connection to the $1. Powered by Claude for natural language, with free direct commands as shortcuts. Architecture Two modes | Mode | Trigger | Cost | Speed | |------|---------|------|-------| | Direct commands | /balance, /bns, etc. | Free | Instant (<1s) | | Natural language | Any text message | Claude API call | 2-5s | Why not use the MCP server's Pillar tools
MCPverified
Public facts
6
Change events
1
Artifacts
0
Freshness
Feb 22, 2026
Verifiededitorial-content1 verified compatibility signal
Published capability contract available. No trust telemetry is available yet. Last updated 2/24/2026.
Schema refs publishedTrust evidence available
Trust score
Unknown
Compatibility
MCP
Freshness
Feb 22, 2026
Vendor
Rapha Btc
Artifacts
0
Benchmarks
0
Last release
1.0.0
Executive Summary
Key links, install path, and a quick operational read before the deeper crawl record.
Summary
Published capability contract available. No trust telemetry is available yet. Last updated 2/24/2026.
Setup snapshot
git clone https://github.com/Rapha-btc/pillar-telegram-bot.git- 1
Setup complexity is MEDIUM. Standard integration tests and API key provisioning are required before connecting this to production workloads.
- 2
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.
Evidence Ledger
Everything public we have scraped or crawled about this agent, grouped by evidence type with provenance.
Vendor (1)
Vendor
Rapha Btc
profilemedium
Compatibility (2)
Protocol compatibility
MCP
contracthigh
Auth modes
mcp, api_key
contracthigh
Artifact (1)
Machine-readable schemas
OpenAPI or schema references published
contracthigh
Security (1)
Handshake status
UNKNOWN
trustmedium
Integration (1)
Crawlable docs
6 indexed pages on the official domain
search_documentmedium
Release & Crawl Timeline
Merged public release, docs, artifact, benchmark, pricing, and trust refresh events.
Artifacts Archive
Extracted files, examples, snippets, parameters, dependencies, permissions, and artifact metadata.
Extracted files
0
Examples
4
Snippets
0
Languages
typescript
Executable Examples
text
User (Telegram) → grammy bot → Claude API (agent loop)
↓
┌─────┴──────┐
│ │
MCP tools Pillar direct
(persistent (API calls,
stdio) URL buttons,
│ bg polling)
↓ ↓
aibtc MCP Pillar API
server (pillar-be)bash
# 1. Install dependencies npm install # 2. Configure .env cp .env.example .env # Set BOT_TOKEN (from @BotFather) # Set ANTHROPIC_API_KEY # Set MCP_SERVER_PATH (path to aibtc MCP server dist/index.js) # Optionally set ALLOWED_USERS (comma-separated Telegram user IDs) # 3. Run npm run dev
bash
sudo cp pillar-bot.service /etc/systemd/system/ sudo systemctl daemon-reload sudo systemctl enable pillar-bot sudo systemctl start pillar-bot # Logs sudo journalctl -u pillar-bot -f
text
src/
├── index.ts # Bot startup, command registration, message routing
├── mcp-client.ts # Persistent stdio MCP connection (Client + StdioClientTransport)
├── claude.ts # Claude API agent loop with tool execution
├── pillar-direct.ts # Direct Pillar API calls, URL buttons, background polling
├── format.ts # Format MCP JSON responses for Telegram
└── commands/
├── wallet.ts # /wallet, /balance, /unlock, /lock, /status
├── transfer.ts # /send, /sendsbtc
├── query.ts # /bns, /tx, /tokens, /network
├── pillar.ts # /connect, /position, /boost, /pstatus, /psend, /supply
└── tools.ts # /tools, /callDocs & README
Full documentation captured from public sources, including the complete README when available.
Docs source
GITHUB MCP
Editorial quality
ready
Telegram bot with persistent MCP connection to aibtc server Pillar Telegram Bot Telegram bot with a persistent MCP connection to the $1. Powered by Claude for natural language, with free direct commands as shortcuts. Architecture Two modes | Mode | Trigger | Cost | Speed | |------|---------|------|-------| | Direct commands | /balance, /bns, etc. | Free | Instant (<1s) | | Natural language | Any text message | Claude API call | 2-5s | Why not use the MCP server's Pillar tools
Full README
Pillar Telegram Bot
Telegram bot with a persistent MCP connection to the aibtc MCP server. Powered by Claude for natural language, with free direct commands as shortcuts.
Architecture
User (Telegram) → grammy bot → Claude API (agent loop)
↓
┌─────┴──────┐
│ │
MCP tools Pillar direct
(persistent (API calls,
stdio) URL buttons,
│ bg polling)
↓ ↓
aibtc MCP Pillar API
server (pillar-be)
Two modes
| Mode | Trigger | Cost | Speed |
|------|---------|------|-------|
| Direct commands | /balance, /bns, etc. | Free | Instant (<1s) |
| Natural language | Any text message | Claude API call | 2-5s |
Why not use the MCP server's Pillar tools directly?
The aibtc MCP server's Pillar tools call openBrowser() to open signing URLs on the local machine. This works in Claude Code (MCP runs locally), but fails when the server runs on a remote machine (like this bot's host). The browser opens server-side where nobody sees it.
Solution: The bot calls the Pillar API directly for handoff operations (pillar-direct.ts):
- Creates the operation via
POST /api/mcp/create-op - Sends the URL as an InlineKeyboard button (opens in external browser, not Telegram's in-app browser)
- Polls
GET /api/mcp/op-status/{opId}in the background - Sends a follow-up message when the operation completes
Non-handoff tools (wallet, balance, transfers, BNS, tokens, DeFi) go through the persistent MCP connection as normal.
Known issue: PILLAR_API_URL default
The aibtc MCP server defaults PILLAR_API_URL to pillarbtc.com (the frontend SPA), which returns 405 for API calls. The correct default is pillar-be.vercel.app. Fix: PR #30.
Setup
# 1. Install dependencies
npm install
# 2. Configure .env
cp .env.example .env
# Set BOT_TOKEN (from @BotFather)
# Set ANTHROPIC_API_KEY
# Set MCP_SERVER_PATH (path to aibtc MCP server dist/index.js)
# Optionally set ALLOWED_USERS (comma-separated Telegram user IDs)
# 3. Run
npm run dev
Run as a service
sudo cp pillar-bot.service /etc/systemd/system/
sudo systemctl daemon-reload
sudo systemctl enable pillar-bot
sudo systemctl start pillar-bot
# Logs
sudo journalctl -u pillar-bot -f
Commands
Free shortcuts (no LLM)
| Command | Description |
|---------|-------------|
| /balance | STX + sBTC balances |
| /wallet | Wallet info |
| /unlock <pw> | Unlock wallet (deletes message) |
| /lock | Lock wallet |
| /bns <name> | BNS name lookup |
| /tx <txid> | Transaction status |
| /tokens | List tokens |
| /tools | List all MCP tools |
| /call <tool> [json] | Call any MCP tool directly |
| /clear | Reset conversation history |
Natural language (Claude)
Just type anything:
- "what's my balance?"
- "send 1 STX to SP2..."
- "connect my pillar wallet"
- "boost 50000 sats"
- "look up whoabuddy.btc"
Pillar handoff commands
These send a button that opens in the external browser for signing:
| Command | Description |
|---------|-------------|
| /connect | Connect Pillar wallet |
| /position | View position |
| /boost [sats] | Boost position |
| /psend <to> <sats> | Send from Pillar |
| /supply [sats] | Supply to Zest |
Project structure
src/
├── index.ts # Bot startup, command registration, message routing
├── mcp-client.ts # Persistent stdio MCP connection (Client + StdioClientTransport)
├── claude.ts # Claude API agent loop with tool execution
├── pillar-direct.ts # Direct Pillar API calls, URL buttons, background polling
├── format.ts # Format MCP JSON responses for Telegram
└── commands/
├── wallet.ts # /wallet, /balance, /unlock, /lock, /status
├── transfer.ts # /send, /sendsbtc
├── query.ts # /bns, /tx, /tokens, /network
├── pillar.ts # /connect, /position, /boost, /pstatus, /psend, /supply
└── tools.ts # /tools, /call
Contract & API
Machine endpoints, protocol fit, contract coverage, invocation examples, and guardrails for agent-to-agent use.
Contract coverage
Status
ready
Auth
mcp, api_key
Streaming
No
Data region
global
Protocol support
MCP: verified
Requires: mcp, lang:typescript
Forbidden: none
Guardrails
Operational confidence: medium
Contract is available with explicit auth and schema references.
Trust confidence is not low and verification freshness is acceptable.
Protocol support is explicitly confirmed in contract metadata.
Invocation examples
curl -s "https://www.xpersona.co/api/v1/agents/mcp-rapha-btc-pillar-telegram-bot/snapshot"
curl -s "https://www.xpersona.co/api/v1/agents/mcp-rapha-btc-pillar-telegram-bot/contract"
curl -s "https://www.xpersona.co/api/v1/agents/mcp-rapha-btc-pillar-telegram-bot/trust"
Reliability & Benchmarks
Trust and runtime signals, benchmark suites, failure patterns, and practical risk constraints.
Trust signals
Handshake
UNKNOWN
Confidence
unknown
Attempts 30d
unknown
Fallback rate
unknown
Runtime metrics
Observed P50
unknown
Observed P95
unknown
Rate limit
unknown
Estimated cost
unknown
No benchmark suites or observed failure patterns are available.
Media & Demo
Every public screenshot, visual asset, demo link, and owner-provided destination tied to this agent.
No screenshots, media assets, or demo links are available.
Related Agents
Neighboring agents from the same protocol and source ecosystem for comparison and shortlist building.
Ard RegistryUpdated 2h agoRank 94
Revuo
Agent-callable B2B SaaS directory: capability-structured, continuously verified listings.
MCPmcpmcp-registry
Ard RegistryUpdated 3h agoRank 94
Inferventis MCP Server
Loan & mortgage calculator, compound interest, ROI, crypto prices, FX conversion for AI agents.
MCPmcpmcp-registry
Ard RegistryUpdated 3h agoRank 94
ShortlistLens
Structured website and review evidence for AI-assisted local-business shortlisting.
MCPmcpmcp-registry
Machine Appendix
Contract JSON
{
"contractStatus": "ready",
"authModes": [
"mcp",
"api_key"
],
"requires": [
"mcp",
"lang:typescript"
],
"forbidden": [],
"supportsMcp": true,
"supportsA2a": false,
"supportsStreaming": false,
"inputSchemaRef": "https://github.com/Rapha-btc/pillar-telegram-bot#input",
"outputSchemaRef": "https://github.com/Rapha-btc/pillar-telegram-bot#output",
"dataRegion": "global",
"contractUpdatedAt": "2026-02-24T19:46:40.188Z",
"sourceUpdatedAt": "2026-02-24T19:46:40.188Z",
"freshnessSeconds": 19618840
}Invocation Guide
{
"preferredApi": {
"snapshotUrl": "https://www.xpersona.co/api/v1/agents/mcp-rapha-btc-pillar-telegram-bot/snapshot",
"contractUrl": "https://www.xpersona.co/api/v1/agents/mcp-rapha-btc-pillar-telegram-bot/contract",
"trustUrl": "https://www.xpersona.co/api/v1/agents/mcp-rapha-btc-pillar-telegram-bot/trust"
},
"curlExamples": [
"curl -s \"https://www.xpersona.co/api/v1/agents/mcp-rapha-btc-pillar-telegram-bot/snapshot\"",
"curl -s \"https://www.xpersona.co/api/v1/agents/mcp-rapha-btc-pillar-telegram-bot/contract\"",
"curl -s \"https://www.xpersona.co/api/v1/agents/mcp-rapha-btc-pillar-telegram-bot/trust\""
],
"jsonRequestTemplate": {
"query": "summarize this repo",
"constraints": {
"maxLatencyMs": 2000,
"protocolPreference": [
"MCP"
]
}
},
"jsonResponseTemplate": {
"ok": true,
"result": {
"summary": "...",
"confidence": 0.9
},
"meta": {
"source": "GITHUB_MCP",
"generatedAt": "2026-10-09T21:27:20.491Z"
}
},
"retryPolicy": {
"maxAttempts": 3,
"backoffMs": [
500,
1500,
3500
],
"retryableConditions": [
"HTTP_429",
"HTTP_503",
"NETWORK_TIMEOUT"
]
}
}Trust JSON
{
"status": "unavailable",
"handshakeStatus": "UNKNOWN",
"verificationFreshnessHours": null,
"reputationScore": null,
"p95LatencyMs": null,
"successRate30d": null,
"fallbackRate": null,
"attempts30d": null,
"trustUpdatedAt": null,
"trustConfidence": "unknown",
"sourceUpdatedAt": null,
"freshnessSeconds": null
}Capability Matrix
{
"rows": [
{
"key": "MCP",
"type": "protocol",
"support": "supported",
"confidenceSource": "contract",
"notes": "Confirmed by capability contract"
}
],
"flattenedTokens": "protocol:MCP|supported|contract"
}Facts JSON
[
{
"factKey": "docs_crawl",
"category": "integration",
"label": "Crawlable docs",
"value": "6 indexed pages on the official domain",
"href": "https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fopenclaw%2Fskills%2Ftree%2Fmain%2Fskills%2Fasleep123%2Fcaldav-calendar",
"sourceUrl": "https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fopenclaw%2Fskills%2Ftree%2Fmain%2Fskills%2Fasleep123%2Fcaldav-calendar",
"sourceType": "search_document",
"confidence": "medium",
"observedAt": "2026-04-15T05:03:46.393Z",
"isPublic": true
},
{
"factKey": "protocols",
"category": "compatibility",
"label": "Protocol compatibility",
"value": "MCP",
"href": "https://www.xpersona.co/api/v1/agents/mcp-rapha-btc-pillar-telegram-bot/contract",
"sourceUrl": "https://www.xpersona.co/api/v1/agents/mcp-rapha-btc-pillar-telegram-bot/contract",
"sourceType": "contract",
"confidence": "high",
"observedAt": "2026-02-24T19:46:40.188Z",
"isPublic": true
},
{
"factKey": "auth_modes",
"category": "compatibility",
"label": "Auth modes",
"value": "mcp, api_key",
"href": "https://www.xpersona.co/api/v1/agents/mcp-rapha-btc-pillar-telegram-bot/contract",
"sourceUrl": "https://www.xpersona.co/api/v1/agents/mcp-rapha-btc-pillar-telegram-bot/contract",
"sourceType": "contract",
"confidence": "high",
"observedAt": "2026-02-24T19:46:40.188Z",
"isPublic": true
},
{
"factKey": "schema_refs",
"category": "artifact",
"label": "Machine-readable schemas",
"value": "OpenAPI or schema references published",
"href": "https://github.com/Rapha-btc/pillar-telegram-bot#input",
"sourceUrl": "https://www.xpersona.co/api/v1/agents/mcp-rapha-btc-pillar-telegram-bot/contract",
"sourceType": "contract",
"confidence": "high",
"observedAt": "2026-02-24T19:46:40.188Z",
"isPublic": true
},
{
"factKey": "vendor",
"category": "vendor",
"label": "Vendor",
"value": "Rapha Btc",
"href": "https://github.com/Rapha-btc/pillar-telegram-bot",
"sourceUrl": "https://github.com/Rapha-btc/pillar-telegram-bot",
"sourceType": "profile",
"confidence": "medium",
"observedAt": "2026-02-24T19:43:14.176Z",
"isPublic": true
},
{
"factKey": "handshake_status",
"category": "security",
"label": "Handshake status",
"value": "UNKNOWN",
"href": "https://www.xpersona.co/api/v1/agents/mcp-rapha-btc-pillar-telegram-bot/trust",
"sourceUrl": "https://www.xpersona.co/api/v1/agents/mcp-rapha-btc-pillar-telegram-bot/trust",
"sourceType": "trust",
"confidence": "medium",
"observedAt": null,
"isPublic": true
}
]Change Events JSON
[
{
"eventType": "docs_update",
"title": "Docs refreshed: Sign in to GitHub · GitHub",
"description": "Fresh crawlable documentation was indexed for the official domain.",
"href": "https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fopenclaw%2Fskills%2Ftree%2Fmain%2Fskills%2Fasleep123%2Fcaldav-calendar",
"sourceUrl": "https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fopenclaw%2Fskills%2Ftree%2Fmain%2Fskills%2Fasleep123%2Fcaldav-calendar",
"sourceType": "search_document",
"confidence": "medium",
"observedAt": "2026-04-15T05:03:46.393Z",
"isPublic": true
}
]