What to prepare
- Verify the current submission and listing-change rules directly; prior research recorded a pause.
- A verified executable submission and result-checking path must exist before this service can offer paid coverage.
An unverified intake is a coverage boundary
Earlier primary research recorded a pause on new entries and listing changes. The submission page returned HTTP 403 during the October 29, 2026 audit, so this check cannot independently confirm its current rules or reopening status. Current search snippets still mention a pause; they do not replace the live submission contract.
This destination therefore stays outside the paid submission set. A service should establish that a real route exists before collecting a fee for execution. Showing an unavailable target in discovery is useful context; representing it as a queued future submission would be misleading.
Keep the upstream registry record accurate
Previously recorded PulseMCP guidance points publishers toward the official MCP Registry. Maintain a correct source identity, release version and connection metadata there if that route fits your server. Those fields remain useful beyond any single downstream catalog.
A registry publication receipt proves the registry action. It does not prove that PulseMCP has imported, reviewed or exposed the entry. Keep those evidence records separate, and avoid describing an anticipated downstream refresh as an existing listing.
Re-check eligibility when the route changes
When intake reopens, review its actual rules and the service’s implemented execution path. Reuse your accurate profile, but run a fresh preflight and inspect the newly proposed scope. No paid launch should quietly inherit a destination that was unavailable when authorized.
For an older existing listing, preserve its public URL and note any stale fields in your own release inventory. That helps a future correction stay focused when listing management becomes available again, without submitting duplicate requests during a pause.
Submission workflow
- Read the current primary submission instructions before planning work for this directory.
- Keep an accurate official MCP Registry record; PulseMCP identifies it as the appropriate first publishing step.
- Exclude PulseMCP from the paid set while intake is paused. Re-run free eligibility checks only after a supported route reopens.
Blockers to resolve before review
Use these as preparation checks. The destination makes its own acceptance decision.
- No current executable submission route has been independently verified by this service.
- A future automatic import is presented as a completed listing or paid submission receipt.
Primary sources
Checked 2026-10-29. Follow the destination’s current instructions if its requirements change.