Jobpost
dev.kanekyv0.2.0Updated Oct 25, 2026
Read the job posting from any career page: title, employer, dates, salary. Paid per call, x402.
Overview
Jobpost reads a job posting from any career page and returns its title, employer, dates and salary, billed per call.
- What you can do
- Extract structured details from a job posting URL on a career page: job title, employer, posting dates and salary information.
- When to use it
- Useful when an assistant needs to pull structured facts from a specific job posting, for example to compare listings or summarize an opening, rather than browsing a whole job board.
- Requirements
- A remote MCP endpoint; no local runtime, account, API key or header is declared. Calls are paid per use through x402, so a payment-capable client is needed.
Installation
In SourceWeft
- Open Jobpost in the dashboard and add it to a workspace.
- 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/dev.kaneky%2Fjobpost/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"jobpost": {
"type": "http",
"url": "https://jobpost.kaneky.dev/mcp"
}
}
}Tools
0Version history
2- v0.2.0LatestOct 18, 2026
- v0.1.1Sep 24, 2026
Score
17% 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
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.