Conversation
|
@cipshadow is attempting to deploy a commit to the Tempo Team on Vercel. A member of the Team first needs to authorize it. |
|
Thanks for submitting a service to the MPP directory! Complete the service pull request template in your PR description before review. It contains the current submission requirements and review criteria. |
🔀 Changed Services✅ Added
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
This listing makes TrueRandomness discoverable to agents that need free MCP random draws or paid random integer certificates with drand quicknet provenance.
Summary
schemas/services.ts.charge,10000base units of USDC.e with 6 decimals.llms.txtreturned HTTP 200.pnpm generate:discoverysucceeds. The same generator script completed directly with the bundled Node runtime and generated a catalog of 138 services.pnpm check:typespasses.pnpm buildsucceeds.pnpmstopped during dependency installation because its active supply-chain check rejected@vercel/cli-config@0.3.0,@vercel/cli-exec@1.0.1, and@vercel/oidc@3.8.9as high-risk trust downgrades. I did not alter the lockfile or bypass that policy. A directtsc --noEmitinvocation could not start type analysis because@types/nodeandunplugin-icons/types/reactwere unavailable in the partial install. Build remains unverified.Key design considerations
chargeon mainnet, USDC.e token0x20c000000000000000000000b9537d11c60e8b50, amount10000, decimals6.cipshadow; support istruerandomnessmcp@proton.me./mcpendpoint exposesrandom_intandstatus; paid HTTP draws return certificates with drand provenance. The listing makes no key-generation or operator-fairness claims.POST /v1/randomuses a fixed UUIDv4 withmin: 0andmax: 1. The live unpaid request returned402with realmverifiable-random-mcp; no payment credential was sent and no payment was made./mcphealth probing is disabled because the directory probe cannot provide the endpoint's requiredAcceptheaders.Follow-up
Run type checking and the production build after the pnpm trust-policy issue is resolved, then confirm paid settlement separately if directory review requires it. The registry generator itself runs without installing project dependencies, while type checking and building do not.