Manifest

io.omfangPublished by omfang.ioOfficial publisherv1.1.3Updated Oct 24, 2026

Turn any webpage into a structured action manifest — clickable, fillable, submittable elements.

VerifiedStreamable HTTPWeb executableBrowser Automation

Overview

AI-generated overview

Lets an assistant turn any webpage into a structured action manifest of clickable, fillable and submittable elements.

What you can do
This remote service turns an arbitrary webpage into a structured action manifest listing the elements that can be clicked, filled in and submitted. An assistant can use that to see which controls a page exposes, as a basis for later automation or workflow planning. The input does not list individual tool names.
When to use it
Use it when an assistant needs to understand or act on a page's buttons, input fields and submit controls rather than just read its text. It also fits workflows that turn web interactions into repeatable structured steps.
Requirements
Needs network access to the remote endpoint at manifest.omfang.io over streamable HTTP. An API key is required and sent in the x-api-key header; the key must be obtained separately. No local package or environment variables are needed.
Before you install
Requires an x-api-key secret, so keep it private and avoid exposing it. The service receives the page content you submit and may send it to a third-party endpoint, so check before using sensitive or internal pages. The input does not say whether it actually operates on or modifies pages.

Installation

In SourceWeft

  1. Open Manifest in the dashboard and add it to a workspace.
  2. Connect x-api-key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.omfang%2Fmanifest/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "manifest": {
      "type": "http",
      "url": "https://manifest.omfang.io/mcp",
      "headers": {
        "x-api-key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.1.3LatestSep 16, 2026

Score

35% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.