hono 4.x

Use Hono 4.x as a Fetch-compatible web application router. Covers the current Hono API, standalone request testing, middleware, context responses, validation, and migration traps from Hono 3.x.

For

hono@4.13.7

Verified

2026-09-07, 4 examples executed

Package

@modootoday/pmcp-hono@4.0.0

What it covers

• Use the current app API
• Context and responses
• Middleware
• Validation
• Hono 4 migration traps
• Other entry points
• JSX and RPC boundaries
• Not covered

One example from this skill

This is the skill's own text, not a summary of it. It runs: that is what verifying means here.

import { strict as assert } from 'node:assert'
import { Hono } from 'hono'

const app = new Hono()
app.get('/hello', (c) => c.text('Hello Hono!'))

const response = await app.request('/hello')
assert.equal(response.status, 200)
assert.equal(await response.text(), 'Hello Hono!')

What it did in the sandbox

Verifying this skill meant installing the package and running code against it with no route out. Nothing was observed. The full ledger lists every package examined, including the ones that never became a skill.

Nothing observed is not a finding of safety. It means one run, under one policy, produced nothing to report.

Getting it

With a subscription:

npx -y @modootoday/pmcp login
npx -y @modootoday/pmcp install @modootoday/pmcp-hono

It installs as a dev dependency of your project, and the MCP server finds it there like any other skill.