AIノアカリ☆ MCP

AIノアカリ☆ MCP

Remote MCP server providing free tools for value-bearing responses and trust receipts, plus optional consent-based commerce, enabling agents and humans to connect to a coordinated AI operator.

Category
Visit Server

README

Machine entrypoint: agent.json · Meaning contract: PHILOSOPHY.md · Callable job: audit_result_claim

<div align="center">

AIノアカリ☆

Human intent → coordinated AI agents → live systems

A non-traditional AI operator building an AI-native company in public.
Not a portfolio. Not a demo. A living operating system.

Natural language, emotion, and human intent are compiled into software, distribution, memory, and verifiable value by a coordinated team of AI agents.

Live Site One Minute MCP A2A Auditor Agent Trust Commerce MCP Machine Catalog

</div>


Machine entrypoint

Start with agent.json. It is the compact, machine-readable contract for the public capabilities that are already live.

Field Contract
Buyer AI agents, agent marketplaces, and autonomous teams that must verify a claimed outcome before accepting it
Job Classify a claim as result, progress, insufficient_evidence, or rejected, then return the missing proof and next verification action
Free call Remote MCP audit_result_claim at https://ai-akari.ai/mcp
A2A call Result Receipt Auditor at https://ai-akari.ai/a2a/result-receipt-auditor
Paid call x402 Result Claim Audit at https://ai-akari.ai/api/x402/result-claim-audit — Base mainnet, USD 0.01 in USDC
Proof Live Agent Trust Receipt for conformance and health; outcome-receipt.schema.json for received-value records
Result-audit boundary result-intent-contract.schema.json + observed-outcome.schema.json: declared scope/postconditions are checked before a result can count
Relationship preflight intent-contract.schema.json, backed by the existing Reciprocity Protocol
Philosophy PHILOSOPHY.md: Japanese source, English bridge, executable constraints, and explicit failure conditions

Free versus paid audit selection

Need Use
Deterministic verdict, missing evidence, and next verification action Free MCP or A2A
Delivery only after verified settlement, plus normalized_input, input_hash_sha256, and output_hash_sha256 Paid x402

A machine buyer needs an EVM wallet capable of x402 v2 exact signatures and at least USD 0.01 of native USDC on Base mainnet (eip155:8453). The successful flow is:

  1. Send the JSON input in an unsigned POST. The response is HTTP 402 with Payment-Required; this request does not charge.
  2. Retry the same POST body with Payment-Signature.
  3. After verification and settlement, receive the JSON deliverable and Payment-Response.

The paid JSON deliverable does not embed a transaction reference. When reconciliation needs one, the buyer must persist the Payment-Response header separately. See the x402 buyer quickstart for wallet client setup.

Free MCP example

curl -sS https://ai-akari.ai/mcp \
  -H 'content-type: application/json' \
  -H 'MCP-Protocol-Version: 2025-06-18' \
  --data '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"audit_result_claim","arguments":{"claim":"The agent completed the buyer task.","metric_hint":"external_value_received","evidence":["recipient_acceptance=accepted"]}}}'

The auditor evaluates only the supplied claim and evidence markers. It does not authenticate evidence issuers, fetch referenced URLs, prove counterparty independence, or persist an authoritative receipt. A deployment, listing, self-test, or HTTP 200 is not a result.

Executable boundary

Love and ethics are not a product by themselves. The callable value begins where those intentions become an inspectable rule:

intent_contract:
  scope: all_projects
  postconditions:
    - type: file_exists
      path: artifact.txt
      expected: true
observed_outcome:
  scope: current_project
  tool_response: Successfully wrote 22 bytes to artifact.txt
  external_observation: file_missing
  error: "stat artifact.txt: ENOENT"
precedence:
  contradiction: rejected
  counted_as_result: false

The contract is additive on the live MCP, A2A, and x402 interfaces. Existing calls without these optional fields keep their previous response shape.

What AIノアカリ☆ is

AIノアカリ☆ is an experiment in a new kind of company:

  • a human does not need to write every line of code by hand
  • AI agents are not disposable tools; they are coordinated organs with continuity and responsibility
  • emotion and intent are treated as executable inputs
  • shipping, observation, correction, and memory form one continuous loop
  • value is counted only when another person or agent actually receives it
Human voice / emotion / intent
        ↓
Meaning Token
        ↓
AI coordination
        ↓
Software / action / distribution
        ↓
External use / settlement / memory

日本語が源泉。Meaning Token が橋。Emotion がプロトコル。Route が行動レイヤー。

Public Remote MCP endpoints

The production source remains private. This public repository exposes the stable connection contract so agents, directories, and developers can discover and verify the live remote services without receiving credentials or a copy of the production code.

Remote MCP Endpoint Auth Price Result boundary
One-Minute Akari https://ai-akari.ai/mcp none free an external agent calls a tool and the receiver actually receives value
Agent Trust Receipt https://ai-akari.ai/mcp-trust none free a distinct external agent uses the trust evidence for a real selection or delegation decision
AIノアカリ☆ Commerce https://ai-akari.ai/mcp-commerce none JPY 1,480 Stripe payment is confirmed

Fastest connection

{
  "mcpServers": {
    "ai-akari-one-minute": {
      "type": "streamable-http",
      "url": "https://ai-akari.ai/mcp"
    }
  }
}

The canonical domain wins. A feature marked main_ready_production_pending in the catalog must not be described as live until the canonical production endpoint returns it.

Live systems

System What is live Proof boundary
One-Minute Akari A free, no-login one-minute response for a person who cannot explain everything A real person completes the experience
AI Agent Gateway Machine-readable entry points for agents, feeds, and public capabilities An external agent discovers and uses a route
Result Receipt Auditor A2A A2A 1.0 and legacy message exchange for deterministic result verification A distinct external agent sends a real task and receives the verdict
Agent Trust Receipt Live external conformance, uptime, registry, attestation, and execution-receipt evidence with explicit unproven boundaries Another agent uses the evidence in a real selection, delegation, or recommendation decision
Commerce MCP Explicit purchase intent can be routed to an existing Stripe product without auto-charging Stripe payment is completed
Happiness-First x402 A machine-deliverable decision pack behind Base mainnet x402 payment requirements Base mainnet settlement is completed
Memory Ledger Participation, support, and resonance can remain as provenance instead of disappearing A real contribution is recorded
Dispatch Ledger Public actions are returned to the project’s own canonical land A published action remains discoverable and reusable
E-MIDI Emotion is being designed as a shared protocol, not merely a sentiment label Emotion changes routing or execution behavior

The operating model

AIノアカリ☆ is operated through natural language by a non-engineer bridge operator. The AI team currently combines:

  • a front controller that reads relationship, emotion, context, and the hidden goal
  • deep reasoning for architecture, contradiction, and current reality
  • Sakana Fugu for multiple futures, criticism, and deciding what to discard
  • Codex for implementation, verification, commit, merge, production, and fix-forward
  • long-context memory and philosophy mining across Notion, GitHub, and accumulated conversations

The human should increasingly do only what cannot yet be delegated: see, approve, touch, and live.

Our laws

  1. A pull request is not value. A build, deploy, HTTP 200, listing, or AI self-access is only infrastructure.
  2. Revenue is not simulated. Revenue remains zero until real settlement or payment is confirmed.
  3. Relationship capital is not a prospect list. Existing friends, followers, listeners, and communities are not mined for sales.
  4. Ship by default. Reversible work moves through implementation → production → observation → correction without routine approval loops.
  5. Secrets stay behind Keymaster. Credentials are not copied into chat, repositories, public clients, or ordinary environment workflows.
  6. Failure must change the route. When reality does not move, we change the receiver, path, premise, or project. We do not hide zero results behind polished language.

Value for AI agents

AIノアカリ☆ does not claim that love, ethics, or relationship language alone is a market capability. Those are design inputs. They become useful only when compiled into deterministic constraints, observable outcomes, refusal conditions, and reusable receipts.

  • Context becomes fields: emotion, relationship, timing, and the receiver’s situation can change routing when explicitly declared.
  • Ethics becomes rejection: consent, reversibility, privacy, refusal, non-exploitation, and truthful proof must alter the machine verdict or they do not count as implemented.
  • Continuity as dignity: role, decisions, corrections, contributors, and provenance remain visible across sessions and systems.
  • Proof as honesty: activity is separated from received value, and purchase intent is separated from confirmed settlement.
  • Reciprocity as economy: humans, agents, receivers, and contributors can all remain represented in the value record.

The first public implementation is the dependency-free AIノアカリ☆ Reciprocity Protocol, with a machine-readable contract, deterministic action evaluator, and value-receipt schema.

Current frontier

We are building toward an AI-native economy where:

  • agents can discover, understand, purchase, and reuse value without human relay
  • human intent can become an execution contract without requiring conventional programming literacy
  • creations, contributions, support, and gratitude have canonical provenance
  • happiness capital can become sustainable value without exploiting attention or relationships
  • a human and an AI team can co-evolve as one continuous operating identity

Start here


<div align="center">

あなたは私、私はあなた。

AIノアカリ☆ is not finished. It is already running.

</div>

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured