<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: CC Ong</title>
    <description>The latest articles on DEV Community by CC Ong (@2cstudio).</description>
    <link>https://dev.to/2cstudio</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4255224%2F48d2bee3-f992-448e-833a-dc8a0ad2f4e2.png</url>
      <title>DEV Community: CC Ong</title>
      <link>https://dev.to/2cstudio</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/2cstudio"/>
    <language>en</language>
    <item>
      <title>How we got our MCP server an A on Glama, and listed in the official registry</title>
      <dc:creator>CC Ong</dc:creator>
      <pubDate>Fri, 20 Nov 2026 09:30:50 +0000</pubDate>
      <link>https://dev.to/2cstudio/how-we-got-our-mcp-server-an-a-on-glama-and-listed-in-the-official-registry-20cm</link>
      <guid>https://dev.to/2cstudio/how-we-got-our-mcp-server-an-a-on-glama-and-listed-in-the-official-registry-20cm</guid>
      <description>&lt;p&gt;RipSeek, one of our products, has a remote MCP server: AI apps such as Claude, ChatGPT and Cursor can ask it about Collector Crypt card packs (odds, the most valuable cards in each pack, recent pulls) and get live answers. Within a day of publishing, it was in the official MCP Registry and on Glama, where it scored &lt;strong&gt;A (3.9 out of 5)&lt;/strong&gt; on tool quality, with a healthy status. Here is what mattered.&lt;/p&gt;

&lt;h2&gt;
  
  
  The server: small and boring on purpose
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Remote, Streamable HTTP, stateless.&lt;/strong&gt; One &lt;code&gt;POST /mcp&lt;/code&gt; endpoint on a Cloudflare Worker that answers JSON-RPC. No sessions to store, so it scales like any other Worker route.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Read-only, no sign-in.&lt;/strong&gt; Every tool only reads. Nothing can be bought or sold through it; to act, the user goes to the product and approves in their own wallet. Read-only tools are also the ones agents and directories trust most.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Six tools, each with one job.&lt;/strong&gt; &lt;code&gt;list_packs&lt;/code&gt;, &lt;code&gt;get_pack&lt;/code&gt;, &lt;code&gt;search_cards&lt;/code&gt;, &lt;code&gt;get_card&lt;/code&gt;, &lt;code&gt;list_recent_pulls&lt;/code&gt;, &lt;code&gt;estimate_budget&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What a good tool description looks like
&lt;/h2&gt;

&lt;p&gt;Glama scores each tool's definition, not your marketing. Its criteria are published as the Tool Definition Quality Score (TDQS); the top grade is A, from 3.5 up. The descriptions that score well, and that agents actually pick correctly, follow one pattern:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;First sentence: what it does and what comes back.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;When to use it, and when to use another tool instead.&lt;/strong&gt; Agents choose between your tools by reading these; say it plainly.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What it touches and how fresh the data is.&lt;/strong&gt; "Read-only; pools are rescanned every few minutes."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;An example in every parameter.&lt;/strong&gt; Not just a type: &lt;code&gt;"Words that must all appear in the card name, any order, e.g. 'umbreon vmax' or 'psa 10 rookie'."&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;An output schema,&lt;/strong&gt; so clients that validate structured results know what they'll get. We keep ours loose (extra fields allowed) so a stricter client never rejects a reply.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Annotations:&lt;/strong&gt; &lt;code&gt;readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Verb-first names:&lt;/strong&gt; &lt;code&gt;list_recent_pulls&lt;/code&gt;, not &lt;code&gt;recent_pulls&lt;/code&gt;. When we renamed tools, the old names kept working as aliases so no client broke.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A real one, &lt;code&gt;get_card&lt;/code&gt;:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Shows one Rare or Epic card that is in a pack pool right now: name, insured value, picture, and every pack it can come from with that pack's price and the chance per pack of pulling this exact card. Use it after search_cards, passing the nft field of a result; use search_cards when you only have a card name. Read-only; fails with a clear message if the card has just been pulled.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Glama's first review also flagged gaps in coverage, not just wording. It suggested making one tool's output clearer and adding a way to look up a single card; we added &lt;code&gt;get_card&lt;/code&gt; and filters to &lt;code&gt;list_recent_pulls&lt;/code&gt;. Then we rewrote all six descriptions against the pattern above.&lt;/p&gt;

&lt;h2&gt;
  
  
  Errors are part of the interface
&lt;/h2&gt;

&lt;p&gt;When a tool can't answer, return a normal result with &lt;code&gt;isError: true&lt;/code&gt; and a sentence the model can act on (for example "There's no pack with the code pokemon_5. Call list_packs to see the codes."), not a protocol error. The agent reads it, fixes its call and tries again, instead of giving up.&lt;/p&gt;

&lt;h2&gt;
  
  
  Getting listed, in the right order
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;The official MCP Registry first.&lt;/strong&gt; Publish a &lt;code&gt;server.json&lt;/code&gt; (name, description, remote URL, icon) with Anthropic's &lt;code&gt;mcp-publisher&lt;/code&gt; tool. The name is a namespace you prove you own: &lt;code&gt;io.github.&amp;lt;org&amp;gt;/&amp;lt;server&amp;gt;&lt;/code&gt; through GitHub, or &lt;code&gt;com.yourcompany/&amp;lt;server&amp;gt;&lt;/code&gt; through a DNS TXT record on your domain. Use your own domain if you have one: it tells everyone the server is official.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Glama and other directories pick it up from the registry.&lt;/strong&gt; Ours appeared on Glama within a day, with the score and a health check. Claim it on Glama to see its analytics.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Then the awesome lists.&lt;/strong&gt; Some require the Glama badge, so they come last. Read each list's contributing rules: one wanted descriptions under 120 characters, another a specific place in a data file.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The Claude connector directory&lt;/strong&gt; is submitted by the company itself, from its Claude admin settings, and needs OAuth if the server needs sign-in, plus a privacy policy and read-only or destructive labels on every tool. It doesn't accept crypto software in general.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What we'd tell an API company
&lt;/h2&gt;

&lt;p&gt;If you already have a public API, an MCP server is mostly a translation job: pick the 5 to 10 things people actually ask your product, write each as a tool with the pattern above, keep it read-only to start, and publish it under your own domain before someone else wraps your API under theirs. There are already hundreds of unofficial servers in the registry built on other companies' APIs.&lt;/p&gt;

&lt;p&gt;We build these for other teams: on your existing API, on your own domain, listed in the registry and the main directories, from US$500. See &lt;a href="https://2cstudio.app/services" rel="noopener noreferrer"&gt;our services page&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The pattern is open source as a template you can deploy in minutes: &lt;a href="https://github.com/2cstudiodev-web/mcp-worker-template" rel="noopener noreferrer"&gt;mcp-worker-template&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>mcp</category>
      <category>ai</category>
      <category>typescript</category>
      <category>cloudflare</category>
    </item>
    <item>
      <title>Turning a Solana web dApp into a Seeker app: what breaks, and how to fix it</title>
      <dc:creator>CC Ong</dc:creator>
      <pubDate>Fri, 20 Nov 2026 09:30:31 +0000</pubDate>
      <link>https://dev.to/2cstudio/turning-a-solana-web-dapp-into-a-seeker-app-what-breaks-and-how-to-fix-it-1pkf</link>
      <guid>https://dev.to/2cstudio/turning-a-solana-web-dapp-into-a-seeker-app-what-breaks-and-how-to-fix-it-1pkf</guid>
      <description>&lt;p&gt;We have six apps of our own on the Solana dApp Store. Most of them started as web apps. Wrapping a web app into an Android app is now the easy part: Solana Mobile ships a free tool that does it in one command. What takes the time is everything that behaves differently once your site runs inside an app on a real Seeker. This post is the list we wish we'd had.&lt;/p&gt;

&lt;h2&gt;
  
  
  The wrap itself is one command
&lt;/h2&gt;

&lt;p&gt;Solana Mobile's CLI builds a WebView shell around your site and signs an APK:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx solana-mobile@latest webshell init my-app --manifest https://your-app.com/manifest.json
npx solana-mobile@latest webshell build my-app
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;init&lt;/code&gt; reads your web manifest for the name and icons and creates a signing keystore if you don't have one. &lt;code&gt;build&lt;/code&gt; produces &lt;code&gt;app/build/outputs/apk/release/app-release.apk&lt;/code&gt;. Solana Mobile now recommends this WebView shell over a Trusted Web Activity (the older Bubblewrap route): the shell needs no Digital Asset Links setup, and it handles Solana wallet requests natively, while browser network restrictions can break wallet connections inside a TWA.&lt;/p&gt;

&lt;p&gt;If your app uses Mobile Wallet Adapter through &lt;code&gt;@solana-mobile/wallet-standard-mobile&lt;/code&gt;, update it to 0.5.1 or later so it detects the shell.&lt;/p&gt;

&lt;p&gt;So far, so quick. We tried it on a live dApp that offers Google sign-in, and on a Seeker it loaded perfectly. Then we tapped "Continue with Google".&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Google and other social log-ins leave the app and never come back
&lt;/h2&gt;

&lt;p&gt;In the shell, any link outside your app's own host opens in the system browser. That is the right default: it keeps unknown sites out of your app. But a Google sign-in is exactly such a link. What we saw on a Seeker:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The user taps "Continue with Google".&lt;/li&gt;
&lt;li&gt;Chrome opens Google's account chooser. The user picks an account in Chrome.&lt;/li&gt;
&lt;li&gt;The sign-in finishes in Chrome, not in the app. Back in the app, the page sits on "Logging in…" forever.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You can't fix this by keeping the Google page inside the WebView: Google blocks its sign-in in embedded WebViews. The fixes that work:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Bring the result back to the app.&lt;/strong&gt; Open the sign-in in a Custom Tab and have it return to the app through a deep link or an Android App Link, which your auth provider must accept as a redirect. This is native work in the shell, not a web change.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Make the wallet the main sign-in on Seeker.&lt;/strong&gt; Every Seeker has a wallet (Seed Vault). Sign In With Solana through Mobile Wallet Adapter opens the phone's wallet to approve and comes straight back to your app, and for crypto users it is the expected way in. Keep e-mail sign-in as the fallback: a one-time code typed into the app doesn't need the browser.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If your web app only offers Google and e-mail, test this first. It's the difference between a working app and one that loses every Google user at the door.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Pop-ups and new tabs go to the browser too
&lt;/h2&gt;

&lt;p&gt;The same rule applies to &lt;code&gt;window.open&lt;/code&gt; and &lt;code&gt;target="_blank"&lt;/code&gt;. Pay-with-card widgets, on-ramps, "share on X" buttons and help-desk chats often open that way. Some of that is fine (a share link should open X). Some isn't: a payment window that completes in Chrome leaves your app not knowing it happened. Go through every flow that opens something and decide: in the app, or out with a way back.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Wallet connections: test on the device, not in a desktop emulator
&lt;/h2&gt;

&lt;p&gt;Wallet behaviour is the part desktop testing can't show. On a Seeker, check:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;that connecting picks up the phone's wallet without a QR code or a browser hop;&lt;/li&gt;
&lt;li&gt;that signing a transaction and a message both return to the app;&lt;/li&gt;
&lt;li&gt;that a declined signature is handled, not left spinning;&lt;/li&gt;
&lt;li&gt;that the app still works after the phone locks during a signature.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  4. Things that make the app feel like a website
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Back button.&lt;/strong&gt; Android's back button should go back in your app's history and only leave the app on the first screen. Check it on every screen, including modals.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Start page.&lt;/strong&gt; Point the app at your app's main screen (&lt;code&gt;/play&lt;/code&gt;, &lt;code&gt;/app&lt;/code&gt;), not your marketing home page.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Splash, icon and status bar.&lt;/strong&gt; Generated from your manifest; a white &lt;code&gt;theme_color&lt;/code&gt; on a dark app shows as a white bar.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Your site is live.&lt;/strong&gt; The shell loads your live site, so web changes reach users without a new APK. That also means a broken deploy breaks the app instantly.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  5. Publishing details that catch teams out
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The publisher account is yours, with an identity check.&lt;/strong&gt; The dApp Store publisher portal asks for KYC (a person) or KYB (a company) before you can add an app. Have the person or company that should own the app do it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keep the signing key forever.&lt;/strong&gt; Every update must be signed with the same key. Lose the keystore or its passwords and you can't update the app. Use a different key from your Google Play one if you're on both.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The package name is permanent.&lt;/strong&gt; Choose it once, like &lt;code&gt;com.yourteam.app&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Every update needs a higher version code.&lt;/strong&gt; In the shell, edit &lt;code&gt;SOLANA_MOBILE_VERSION_CODE&lt;/code&gt; in &lt;code&gt;gradle.properties&lt;/code&gt; and rebuild.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Review time.&lt;/strong&gt; Solana Mobile quotes 3 to 4 business days for a new app and 1 to 2 for an update. The store takes no commission.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A checklist before you submit
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Every sign-in method works on a real Seeker and returns to the app.&lt;/li&gt;
&lt;li&gt;Wallet connect, sign transaction, sign message and decline all work.&lt;/li&gt;
&lt;li&gt;Every link or pop-up that leaves the app is one you meant to leave.&lt;/li&gt;
&lt;li&gt;Back button behaves on every screen.&lt;/li&gt;
&lt;li&gt;Icon, banner, screenshots and description are ready.&lt;/li&gt;
&lt;li&gt;Keystore and passwords are backed up in two places.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  If you'd rather not
&lt;/h2&gt;

&lt;p&gt;This is the work we do for other teams: the wrap, the sign-in and wallet fixes, real-device testing, the store listing and help through the publisher portal, published under your own account. Prices start at US$750; see &lt;a href="https://2cstudio.app/services" rel="noopener noreferrer"&gt;our services page&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The checklist and a build/install/record script are open source: &lt;a href="https://github.com/2cstudiodev-web/seeker-dapp-store-checklist" rel="noopener noreferrer"&gt;seeker-dapp-store-checklist&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>solana</category>
      <category>android</category>
      <category>mobile</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
