Emboss is the official remote MCP server from getemboss.ai. It answers at https://api.getemboss.ai/mcp over streamable HTTP and asks you to sign in with your getemboss.ai account before it lists its tools, so your client opens a login the first time it connects. Our probes reached it 11 of 11 times since 4 September 2026; the last check, on 25 October 2026, got the sign-in challenge, so it is up.
Turn a flat or scanned PDF form into a fillable PDF with detected fields. Fill a PDF form from structured data such as JSON or key-value answers. Fill a PDF form using facts found in supporting documents. Prepare a form from documents: a proposal of every answer with its source, what is missing, and where documents disagree, before writing, plus attachments for a package. Fill one copy of a PDF form for every row of a spreadsheet. Propose which spreadsheet columns fill which PDF form fields. Write or confirm the answers, render the form with text that fits, check it, and return the PDF with a
Description as the publisher wrote it.
A sign-in. The server refused to list its tools to an anonymous client and answered with an authentication challenge, which is how an MCP server protected by OAuth behaves. Add it with one of the setups below; the first connection opens a login for your getemboss.ai account, and the tools appear once you have approved it.
Every block below points at https://api.getemboss.ai/mcp. Pick your client and copy.
claude mcp add --transport http emboss https://api.getemboss.ai/mcp
{
"mcpServers": {
"emboss": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.getemboss.ai/mcp"]
}
}
}{
"mcpServers": {
"emboss": {
"url": "https://api.getemboss.ai/mcp"
}
}
}{
"servers": {
"emboss": {
"type": "http",
"url": "https://api.getemboss.ai/mcp"
}
}
}{
"context_servers": {
"emboss": {
"url": "https://api.getemboss.ai/mcp"
}
}
}{
"mcpServers": {
"emboss": {
"serverUrl": "https://api.getemboss.ai/mcp"
}
}
}{
"mcpServers": {
"emboss": {
"url": "https://api.getemboss.ai/mcp"
}
}
}name: Emboss
version: 0.0.1
schema: v1
mcpServers:
- name: Emboss
type: streamable-http
url: https://api.getemboss.ai/mcp{
"mcpServers": {
"emboss": {
"httpUrl": "https://api.getemboss.ai/mcp"
}
}
}{
"mcpServers": {
"emboss": {
"type": "http",
"url": "https://api.getemboss.ai/mcp"
}
}
}{
"mcpServers": {
"emboss": {
"url": "https://api.getemboss.ai/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapi.getemboss.ai%2Fmcp&type=streamable_http&id=emboss&name=Emboss
It answered our last check on 25 October 2026 in 289 ms. Over 11 checks since 4 September 2026 it answered 11. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by getemboss.ai and served from api.getemboss.ai, the vendor's own domain: https://api.getemboss.ai/mcp.
Add the server with a setup above. The first time your client connects it opens the sign-in page for getemboss.ai; approve it and the tools load.
It answered our last check on 25 October 2026 in 289 ms. Over 11 checks since 4 September 2026 it answered 11.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.getemboss.ai/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It needs a sign-in rather than a key you paste: the server answered with an authentication challenge, so your client runs the login when it first connects.
Publisher: getemboss.ai. Endpoint host: api.getemboss.ai. ARD identifier: urn:air:getemboss.ai:mcp:emboss.
First indexed 4 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.