GenHTTP Lambda
v0.1.0Write, deploy and host small C# web services and sites at a public address.
Endpoint health
online- Last checked
- 11/20/2026, 8:18:46 AM
- Latency
- 284 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:dev.genhttp%2Flambda
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"dev.genhttp/lambda": {
"url": "https://genhttp.dev/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
25 shown · authentication unknown
Read who visits a lambda
analytics
How people reach a lambda, as its owner sees it in the editor: visitors, pages opened and requests per day, and the pages, referring sites, countries, devices, browsers, operating systems and crawlers (search engines, AIs, link previews) behind them. Counted by day in UTC and written down every few minutes; a year is kept, of which the lambda's tier decides how much is shown (platform_guide, analytics). Off until switched on - nothing is counted before. enable: true switches it on, only when the user asks; switching off deletes what was counted and is the owner's to do in the editor. Use it to answer what the user asks about their visitors, or to see which pages matter before changing them.
Schema valid · SHA-256 8236d8d2aca4…
View input schema
{ "type": "object", "properties": { "privateKey": { "description": "The editor key.", "type": "string" }, "days": { "description": "How many days, today included. Left out, as many as the lambda's tier shows, which is also the most.", "type": [ "integer", "null" ] }, "enable": { "description": "Switch analytics on, counting from the next request - only when the user asked for it.", "type": "boolean", "default": false } }, "required": [ "privateKey" ] }Change some files
change_code
Change some files: add or replace files, remove files, or replace text within a file. Everything not named stays as it is, so there is no need to resend unchanged files. With feature, the change is saved into that feature - the way to work on a lambda that exists: change it as often as you like, deploy: true to try it at the feature's preview address, merge_feature when it is right. Without feature, the newest version is changed and saved as a new version. Update what the change affects in docs/ and tests/ in the same change - an edit of a passage is enough. check: true compiles without publishing. Code that does not compile is saved but never goes online.
Connections
streamable-http
https://genhttp.dev/mcp