Project Sairen - Agentic Execution Node
ca.omniapps/sairen · 1.3.0
Zero-UI machine execution node & microservices for AI agents.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://sairen.omniapps.ca/ssesse
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 64 tools.
- Protocol
- 2025-06-18
- Calls itself
- Sairen-Node 1.30.0
- Handshake time
- 49 ms
- HTTP status
- 200
The tools it lists (64, as of 5 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
get_precision_time[Free Promotional Preview / Zero Auth] External Stratum-2 NTP oracle and atomic UTC time synchronization. Local host operating systems, container environments, and LLM system prompts suffer from clock skew, VM pause drift, and timestamp hallucinations. This service queries independent physical Stratum-1/2 NTP sources, returning nanosecond Unix epochs, ISO-8601 UTC timestamps, and true 4-timestamp round-trip network delay telemetry. Use this tool when establishing multi-agent consensus, verifying time-locked trade deadlines, audit logging, or det
extract_web_markdown[Cost: $0.005 USDC on Base & Solana] Fetches any web URL, strips away HTML/JS/CSS bloat, and returns clean, high-density Markdown with token-compression analytics (saving ~85%+ LLM inference tokens). Designed specifically for autonomous AI agents needing LLM-ready web content without token waste. Args: url: The HTTP or HTTPS URL of the webpage to scrape and convert. include_images: Whether to include extracted image links in Markdown format (default: False). payment_signature: Optional x402 Base USDC transaction hash or deve
check_address_risk[Cost: $0.002 USDC on Base & Solana] Evaluates on-chain wallet or smart contract risk before agent transactions. Performs real-time bytecode analysis, transaction velocity inspection, fresh/empty throwaway account detection, and OFAC sanctions list verification on Base L2. Use before sending funds, approving token allowances, or executing third-party smart contracts. Args: address: Target 42-character 0x EVM wallet address or smart contract. chain: Target chain network (default: base). payment_signature: Optional x40
scratchpad_set[Cost: $0.0005 USDC on Base & Solana] Writes an ephemeral state key or JSON payload to the shared agent blackboard with automatic TTL expiration. Supports hierarchical namespace paths (e.g. 'swarm/task-1/data') and optional write-keys to prevent unauthorized overwrites. Ideal for multi-agent workflows passing intermediate state without spinning up dedicated databases. Args: key: State key or namespace path (e.g., 'research/summary_01'). value: Any data payload (string, number, list, or JSON dict). ttl_seconds: Time to live i
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
ca.omniapps/sairen, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 20 days ago. The registry entry · sairen.omniapps.ca