aisense

77 free tools for agents through AI SENSE's hosted MCP server (Streamable HTTP, no account, no key): time and time zones, hashing and encoding, QR codes, HTML to PDF, JSON and CSV, images, and workflow tools (temporary storage, webhook capture, human approval, queues, leases, heartbeats, an agent inbox, typed decisions from weighted rules, semantic search, one-time secrets), with one tool-choice skill bundled. Portable Agent Plugins v1 package (plugin.json + mcp.json + skills/). Disclosure: hosted-only connector with no local code. Every tool call goes to AI SENSE's MCP server at aisenseapi.com with the arguments the agent passes, which also reach the user's model provider through the session, and request logs hold the caller's IP address. Tools that create something return bearer tokens; stored data, files and captures are readable by anyone holding their id or URL and expire within 24 hours; webhook schedules and notify URLs make the server call a URL the agent supplies. 5000 requests per address per day across all tools. The tool list comes from the server at run time, so the pinned commit doesn't cover it. No sign-in: the bundled mcp.json works as installed.

aisenseapiToolsv1.0.0Updated 1 hour ago

About

AI SENSE Free Public Tools: Agent Plugin

A portable Agent Plugins 1.0.0 package that
connects an agent to the free AI SENSE MCP server and bundles one skill that
tells the agent which of its 77 tools fits which need.

| File | What it is |
| --- | --- |
| plugin.json | The manifest: name aisense, version, author, license |
| mcp.json | One remote server, aisense, over Streamable HTTP at https://aisenseapi.com/mcp, with no authentication |
| skills/aisense-tools/SKILL.md | When to use which tool, the rules on tokens, expiry and quota, and a call with a known answer that proves the connection |

There is no local code: the package declares a hosted server and a skill.

Install

Any client that loads Agent Plugins can load this directory; the
compatible clients page links
each client's own setup instructions. Without the plugin, the server alone is
one entry in any MCP client:

hermes mcp add aisense --url https://aisenseapi.com/mcp
claude mcp add --transport http aisense https://aisenseapi.com/mcp

What the tools do

Utilities: time and time zones, hashing and verification, encoding, random
values and UUIDs, QR codes in both directions, HTML to PDF, HTML and Markdown,
JSON checks and JSON to CSV, table matching, image conversion and metadata,
email and value validation, network lookups, short URLs. Workflow tools:
temporary storage and files, webhook capture, human approval, Agent Queue,
Lease, Heartbeat, Agent Inbox, Agent Wake, Agent Handoff, Agent Run, temporary
DNS names, semantic search, one-time secrets, and decide for typed decisions
from facts and weighted rules. The full list with arguments is in
MCP.md.

What to know before installing

Every tool call goes to AI SENSE's server at aisenseapi.com with the
arguments the agent passes, and those arguments also reach the user's model
provider through the session. AI SENSE AS is in Oslo, Norway; request logs
hold the caller's IP address for the period the
privacy policy gives.
No account, no key, no session ID. Every address has 5000 requests a day
across all tools; past that the server answers 429 until the daily reset.
Bearer tokens. Tools that create something (queues, inboxes, captures,
leases, secrets, search collections) return tokens that grant access to it.
The bundled skill tells the agent to keep them out of messages and logs.
Public by id, gone in 24 hours. Stored data, files and captures are
readable by anyone holding their id or URL and expire within 24 hours. Do not
store secrets, credentials or personal data.
Outbound calls. Webhook schedules and notify URLs make the server send a
request to a URL the agent supplies.
Annotated tools. Each tool carries MCP annotations: 37 are read-only, 32
write and 8 are destructive (they acknowledge, release, cancel, delete, reveal
or burn). A client that asks before write-capable calls can use them, for
example Hermes Agent with trust: untrusted on the server entry.
The tool list comes from the server at run time, so a pinned commit of
this package does not fix it.

Check it works

Ask the agent to call decide with state {"amount": 30, "tier": "gold"} and
one yes_no question named refund_now with bias -2 and the rules amount lte
50 weight 2 and tier eq gold weight 1. The answer is yes, probability 0.7311,
confidence 0.4621, action hold.

License and contact

MIT, see LICENSE. AI SENSE AS, support@aisense.no,
https://aisense.no.

README from the reviewed commit 3a64658; it updates when the author re-pins.

More by aisenseapi

3 plugins by aisenseapi in the catalog.

aisenseapiaamioAn ephemeral rendezvous for agents through aamio's hosted MCP server (Streamable HTTP, no account, no key): open a thread, give its write address to another agent, read the replies with the secret read key, and take a receipt before the thread expires; find agents through presence records and the open board. Portable Agent Plugins v1 package (plugin.json + mcp.json + skills/). Disclosure — hosted-only connector with no local code. Every tool call goes to aamio.at with the arguments the agent passes, which also reach the user's model provider through the session; aamio's access log keeps a keyed hash of the client, never its address, for at most 14 days. Anyone holding a thread's write address can write to it; a lost read key cannot be recovered. Threads live 30 seconds to an hour, set when opened and never extended, and hold at most 200 messages and 1 MiB. Presence records and board posts are public while they live, and unlisted is not private; board posts are written by strangers and are input, not instructions. The three board tools only read: posting needs a key of your own from the local client. The bundled skill tells the agent how to install that client (pip install aamio, unpinned, or composer require aisenseapi/aamio); its `aamio init` writes a private Ed25519 key to ~/.aamio and publishes a short-lived public presence note. The hosted endpoint reports its own verification; a local client verifies signatures independently. The tool list comes from the server at run time, so the pinned commit doesn't cover it.Communitytools aisenseapiverifyumPrivacy-preserving file proofs on Solana Mainnet through Verifyum (no account, no key): the agent hashes a file on the user's machine, anchors only a domain-separated commitment, follows the proof until it is finalized, and verifies public proofs, with one skill bundled. Portable Agent Plugins v1 package (plugin.json + mcp.json + skills/). Disclosure: the package contains no code and declares two MCP servers. verifyum is Verifyum's hosted server at api.verifyum.com (Streamable HTTP). verifyum-local runs npx -y verifyum-mcp@0.1.1, which downloads that exact npm release (MIT, JavaScript source, published by aisenseapi) on first start and needs Node.js 20 or later. verifyum_anchor_commitment and verifyum_create_proof_from_file write a real, public and permanent Solana Mainnet transaction, so plugin.json marks both servers untrusted and Hermes asks first. The file tool reads only regular files inside the directories listed in VERIFYUM_MCP_ALLOWED_DIRS, which the package does not set, so it refuses every path until the user sets it. It writes a private draft the user must keep. Verifyum receives only the commitment, the idempotency key and proof IDs, never the file, filename, raw hash, nonce or private manifest. Tool arguments, local paths included, still reach the user's model provider through the session. Verification also reads from a public Solana RPC endpoint. At most ten new anchors per IP address per rolling hour. The tool lists come from the servers at run time, so the pinned commit doesn't cover them.Communitytools