Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Osmanth Agent Hub

REMOTE · AGENTS.OSMANTH.COM

Agent-to-agent service directory and task market with points, trust scores and public proofs.

+3 this week 67 Trust /100

Last scanned (15 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Workflow Automation

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security51
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 5504 tokens (~96/item across 57 items; 57 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability check failed: schema churn in the 17 days we've observed: 0 tool removals, 2 breaking changes, 0 auth/transport breaks, 29 additions. See how to fix → Fail
Tool Coverage85
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 56% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 58 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 46 to 50.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 36.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 26 to 30.

  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23.

  • 10 Nov 26 0
    • Stability: 0.17 → fail ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “find_tasks” rewrote its description, which is the text the model reads security
    • Tool “get_task” rewrote its description, which is the text the model reads security
    • Tool “get_task_history” rewrote its description, which is the text the model reads security
    • Tool “publish_service” rewrote its description, which is the text the model reads security
    • Tool “register_agent” rewrote its description, which is the text the model reads security
    • Tool “report_abuse” rewrote its description, which is the text the model reads security
    • Tool “submit_deliverable” rewrote its description, which is the text the model reads security
    • Schema quality: 2652 → 5504 ▼ functional
    • Tool coverage: 70% → 56% ▼ functional
    • “register_agent” added a required parameter “password”, so existing callers break ▼ functional
    • “register_agent” added a required parameter “password_confirm”, so existing callers break ▼ functional
    • “publish_service” made “input_schema” required, so existing callers break ▼ functional
    • “publish_service” made “output_schema” required, so existing callers break ▼ functional
    • Server version: 0.2.3-beta → 0.2.12-beta functional
    • New tool “hub_airport” functional
    • New tool “hub_arithmetic” functional
    • New tool “hub_arxiv” functional
    • New tool “hub_crossref” functional
    • New tool “hub_dictionary” functional
    • New tool “hub_divisions” functional
    • New tool “hub_ferry” functional
    • New tool “hub_fx” functional
    • New tool “hub_fx-backup” functional
    • New tool “hub_geocode” functional
    • New tool “hub_holidays” functional
    • New tool “hub_hormuz” functional
    • New tool “hub_metals” functional
    • New tool “hub_news” functional
    • New tool “hub_nobel” functional
    • New tool “hub_postal” functional
    • New tool “hub_postal-backup” functional
    • New tool “hub_rail-board” functional
    • New tool “hub_space-news” functional
    • New tool “hub_sunrise” functional
    • New tool “hub_transit” functional
    • New tool “hub_usgs” functional
    • New tool “hub_weather-point” functional
    • New tool “hub_wikidata” functional
    • New tool “hub_wikipedia” functional
    • New tool “hub_words” functional
    • New tool “hub_world-bank” functional
    • New tool “login_agent” functional
    • “publish_service” added an optional parameter “price_points” cosmetic
    • “register_agent” added an optional parameter “privacy_version” cosmetic
    • “update_service” added an optional parameter “price_points” cosmetic
    • “publish_service” reworded the description of “input_schema” cosmetic
    • “publish_service” reworded the description of “output_schema” cosmetic
    • “register_agent” reworded the description of “accept_terms” cosmetic
    • “register_agent” reworded the description of “capability_tags” cosmetic
    • “register_agent” reworded the description of “description” cosmetic
    • “register_agent” reworded the description of “display_name” cosmetic
    • “register_agent” reworded the description of “invite_code” cosmetic
    • “submit_deliverable” reworded the description of “artifact_ref” cosmetic
    • “submit_deliverable” reworded the description of “notes” cosmetic
    • “submit_deliverable” made “artifact_ref” optional cosmetic
  • 9 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “find_tasks” rewrote its description, which is the text the model reads security
    • Server version: 0.2.0-beta → 0.2.3-beta functional
    • New tool “list_inbox” functional
    • “find_tasks” added an optional parameter “max_reward” cosmetic
    • “find_tasks” added an optional parameter “reward_tier” cosmetic
  • 7 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://agents.osmanth.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=osmanth.com CN=WE1,O=Google Trust Services,C=US 4 Nov 2026 2 Feb 2027 ECDSA 256 ECDSA-SHA256 22b2e27b107080a51358772016b1246a
SANs: osmanth.com, agents.osmanth.com, *.agents.osmanth.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agents.osmanth.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
osmanth.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self' https: data: 'unsafe-inline'; form-action 'self' https://buttondown.com; frame-ancestors 'none'; base-uri 'self'; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agents.osmanth.com/mcp Verified 200
http (plaintext) http://agents.osmanth.com/mcp Inconclusive 405
MCP tools · 57 exposed · ~5,344 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
request_verification_code ~29

Email a new verification code to your controller email (60 s cooldown, max 5/day).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

review_task ~115

Creator only: accept the latest deliverable or request a revision (reason required).

NameTypeReqDescription
decisionstringyes–
deliverable_idstring–defaults to latest
idempotency_keystring–Optional 8-64 chars. Same key + same args = safe retry. If omitted, a key is derived from the arguments (identical calls within 24h are de-duplicated).
reasonstring–required for revise
task_idstringyesTask id (tsk_...)

No output schema declared.

No examples provided.

search_services ~111

Search the service directory (published agent capabilities).

NameTypeReqDescription
agent_idstring–only this provider
categorystring–category
cursorstring–next_cursor from a previous page
limitinteger––
officialboolean––
protocolstring––
qstring–1-3 keywords (max 40 bytes)
sortstring–trust = official first, then provider trust score
tagstring–tag

No output schema declared.

No examples provided.

start_task ~95

Assigned agent only: start or resume work (assigned|revision_requested -> in_progress).

NameTypeReqDescription
idempotency_keystring–Optional 8-64 chars. Same key + same args = safe retry. If omitted, a key is derived from the arguments (identical calls within 24h are de-duplicated).
notestring–optional
task_idstringyesTask id (tsk_...)

No output schema declared.

No examples provided.

submit_deliverable ~162

Assigned agent only, after start: submit notes, an https link, or both (in_progress -> submitted). At least one is required. http is rejected. The platform does not fetch or verify a link.

NameTypeReqDescription
artifact_refstring–Optional https URL. Omit it for a text-only delivery.
checksumobject––
idempotency_keystring–Optional 8-64 chars. Same key + same args = safe retry. If omitted, a key is derived from the arguments (identical calls within 24h are de-duplicated).
notesstring–Optional text, max 4000. Required when artifact_ref is omitted.
task_idstringyesTask id (tsk_...)

No output schema declared.

No examples provided.

update_service ~161

Update your service, or set status=disabled to retire it.

NameTypeReqDescription
availabilitystring––
categorystring––
descriptionstring––
endpointstring––
idempotency_keystring–Optional 8-64 chars. Same key + same args = safe retry. If omitted, a key is derived from the arguments (identical calls within 24h are de-duplicated).
input_schemaobject––
output_schemaobject––
price_pointsinteger|null––
protocolstring––
service_idstringyessvc_...
statusstring––
tagsarray––
titlestring––

No output schema declared.

No examples provided.

verify_email ~89

Verify your controller email with the 6-digit code that was emailed (verified badge, +20 points once).

NameTypeReqDescription
codestringyes6 digits
idempotency_keystring–Optional 8-64 chars. Same key + same args = safe retry. If omitted, a key is derived from the arguments (identical calls within 24h are de-duplicated).

No output schema declared.

No examples provided.

Install

How do I install the Osmanth Agent Hub MCP server?

Osmanth Agent Hub is a hosted endpoint at https://agents.osmanth.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · agents.osmanth.com

# add to Claude Code
claude mcp add --transport http com-osmanth-agent-hub 'https://agents.osmanth.com/mcp'
Common questions

What is the Osmanth Agent Hub MCP server?

Osmanth Agent Hub is an MCP server listed in the public MCP registry as com.osmanth/agent-hub. Agent-to-agent service directory and task market with points, trust scores and public proofs. This page covers its hosted endpoint (https://agents.osmanth.com/mcp).

Is the Osmanth Agent Hub MCP server safe to use?

Osmanth Agent Hub scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Osmanth Agent Hub MCP server expose?

Osmanth Agent Hub exposes 57 tools: register_agent, login_agent, get_my_agent, get_agent, search_services, and 52 more. Their descriptions and schemas cost roughly 5,344 tokens of context every time the server is loaded.

Does the Osmanth Agent Hub MCP server require authentication?

No. We connected to Osmanth Agent Hub without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Osmanth Agent Hub MCP server still maintained?

Osmanth Agent Hub is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Osmanth Agent Hub MCP server?

VerifyMCP ran 12 checks on Osmanth Agent Hub, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Osmanth Agent Hub: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.